Fix dependency conflict with Next.js package #795
Merged
Conversation
This file contains 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
🦋 Changeset detectedLatest commit: 6b69e15 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 |
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
ijjk
added a commit
to vercel/next.js
that referenced
this pull request
Feb 5, 2024
See here for additional context vercel/edge-runtime#795 but TLDR is due to a bug in the `npmcli` we aren't able to publish Next.js releases after this package was upgraded. We can re-land the upgrade after that PR is landed/published. Reverts #61030 Closes NEXT-2367
|
Thanks for taking care @ijjk 🙏 |
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Currently we are unable to publish any Next.js versions that include the
jest-environmentpackage in the tree due to a bug in thenpmclithat attempts resolving the dependency tree during a publish but fails to handle a circular dependency.Hoisting the
nextdevDependencyto the root should resolve this issue.x-ref: slack thread