fix(nuxt): resolve builder using esm syntax#19608
Merged
Merged
Conversation
|
|
pi0
reviewed
Mar 13, 2023
|
|
||
| async function loadBuilder (nuxt: Nuxt, builder: string) { | ||
| for (const root of [nuxt.options.rootDir, import.meta.url]) { | ||
| const builderPath = await tryResolveModule(builder, root) |
Member
There was a problem hiding this comment.
I think we can pass search path directly to the kit util (at least mlly reslver supports it)
This was referenced Mar 13, 2023
Merged
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.
🔗 Linked issue
❓ Type of change
📚 Description
Similar to #19601, we also need to resolve
@nuxt/vite-buildervia rootDir/nuxt.📝 Checklist