fix(builder): use require.resolve to get the path of babel-loader #4150
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.
Types of changes
Description
Yarn sometimes tries to move packages into a subpackage. (yarn moved
babel-loader
dependency intonode_modules/@nuxt/builder-edge/node_modules/babel-loader
when upgraded a project) This break builds when resolving webpack loaders because they are being required from root package nuxt builder.This PR is the same as a workaround for
'@nuxtjs/babel-preset-app'
/NPX. Only targetting babel loaders as they are more likely to move into the builder.Checklist: