fix(nuxt): fix import path of named components #25282
Merged
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
resolves #25281
β Type of change
π Description
If a component is registered as client-only then when scanning a placeholder is created for it on server-side:
nuxt/packages/nuxt/src/components/module.ts
Line 175 in 2bfe01d
When loading this component the import path depends on the
export
property:nuxt/packages/nuxt/src/components/loader.ts
Line 79 in 2bfe01d
The problem is that the placeholder is exported as
default
and the component is exported as named. So the import path is incorrect.π Checklist