fix(migrate): specify full version ranges for @next packages - #1292
Merged
Conversation
|
Install the latest version of pnx https://pkg.svelte.dev/sv/c/e77af83291594c860c8c24a88a1bcba8dacf43cd createOpen in |
🦋 Changeset detectedLatest commit: e77af83 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
AdrianGonz97
marked this pull request as ready for review
August 24, 2026 15:16
jycouet
approved these changes
Aug 24, 2026
jycouet
left a comment
Contributor
There was a problem hiding this comment.
TIL ^x.y.z-next.0 is working!
Nice
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #1283
One small quirk is if they have a package that has
@sveltejs/kit@^2as a peer-dependency (e.g.better-auth), then an install withnpmwill fail without the--legacy-peer-depsflag.We could pass it automatically as part of
npm install(which can work), however, all subsequentnpm install's by the user will fail if they don't provide the flag themselves, which can be confusing if they're not educated about it. I wonder if we should log out some info telling them about it? ...but then we'd have to be able to detect if the install failed for that very reason, so we may be falling down an annoying rabbit hole just for that.Checklist