fix(wrangler): use require.resolve to resolve unenv path #7804
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.
This PR fixes an issue with unenv resolution introduced in #7625 that could break some Nuxt apps built with
wrangler
v3.100.0 ... v3.103.1.This fix should go in v3.103.2 tomorrow.
If you previously built a Nuxt app with any of the affected wrangler versions, please rebuild it with either wrangler v3.99 or with v3.103.2 when it is released.
To detect the issue, you should dump
aliasAbsolute
inwrangler/wrangler-dist/cli.js
.Faulty releases import
unenv
from different paths/versions: