-
Notifications
You must be signed in to change notification settings - Fork 400
chore: Bump svelte peer dependency #1006
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
Conversation
|
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
1 Skipped Deployment
|
WalkthroughThe pull request updates the Changes
Assessment against linked issues
Possibly related PRs
📜 Recent review detailsConfiguration used: CodeRabbit UI ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (2)
🚧 Files skipped from review as they are similar to previous changes (2)
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
| ], | ||
| "peerDependencies": { | ||
| "svelte": "^4.0.0", | ||
| "svelte": "^4.0.0 || ^5.0.0-next.0", |
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.
When is this expected to land as stable? I don't know many libs that include prereleases in their peer dep range (e.g React 19 and Next 15 you just have to deal with 100 packages yelling).
Also since none of us are familiar with Svelte we don't wanna bump this and have an expectation to fix it if they introduce some breaking change before official release
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 cannot say when will it land as stable, but it has been in RC state for a while now so I would soon-ish. v5 should be fully compatible with v4 so even if a breaking change is introduced it would only affect v5 specific features not the v4 ones.
Also, the sveltekit package includes the very same peer dependency for svelte as this PR introduces, so I would say it's pretty safe. For reference: https://github.com/sveltejs/kit/blob/main/packages/kit/package.json
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 👍 I'll let @markflorkowski have the final say
Can you elaborate on this @AlanAcDz ? Is it something that can be done once stable is out or what's blocking it? |
juliusmarminge
left a comment
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.
Would like either @markflorkowski or @t3dotgg to approve bumping peer dep to a preview release
|
Mark approved |
This reverts commit adb002c.
Yeah, both the sveltekit example and the svelte package use svelte v4 atm, if you bump only the example version it breaks the build of the package because of how the monorepo manages dependencies. |
Bump svelte peer dependency to include svelte 5 RC, closes #967
I would have liked to also bump the svelte version on the sveltekit example to make it easier to test, but it would break the build of the svelte package afterwards.
Summary by CodeRabbit