feat(nuxt): allow auto-registration of plugins with .jsx or .tsx extensions #26230
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.
β Type of change
π Description
This PR adds
.jsx
and.tsx
to the list of extensions that are automatically resolved in theplugins
directory.Additionally, in order to avoid the meta data analysis from throwing an error (and therefore a
WARN Failed to parse static properties from plugin xxxxx
), I switched the esbuild transform loader fromts
totsx
.The plugin metadata test has been updated in a not-very-elegant way, but I though it was better than changing the test to
.tsx
"just" for 3 words.π Checklist