-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore(sveltekit): Add SvelteKit 2.0 to peer dependency range #9861
Conversation
packages/sveltekit/package.json
Outdated
@@ -17,7 +17,7 @@ | |||
"access": "public" | |||
}, | |||
"peerDependencies": { | |||
"@sveltejs/kit": "1.x" | |||
"@sveltejs/kit": ">=1.x" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
To be a bit more cautious, should we make this >= 1 <= 2
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We can ofc but for example, in Astro, we opted to leave an open end given that we'll need support for a new major anyway (#9683)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
fine with me 👍
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd rather we explicitly opt-in to every major version, and make this "@sveltejs/kit": "^1.0 || ^2.0"
like what we do for nextjs.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ok, changed it to an explicit major array. Don't have strong opinions here, so fine with anything 😅
6409323
to
48fbe6b
Compare
Setting the range to
>=1.x
to include kit 2.0 and higher1.x || 2.x
to include kit 2.0