Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

toyi
Copy link
Contributor

@toyi toyi commented Mar 13, 2024

❓ Type of change

  • πŸ“– Documentation (updates to the documentation, readme or JSdoc annotations)
  • 🐞 Bug fix (a non-breaking change that fixes an issue)
  • πŸ‘Œ Enhancement (improving an existing functionality like performance)
  • ✨ New feature (a non-breaking change that adds functionality)
  • 🧹 Chore (updates to the build process or auxiliary tools and libraries)
  • ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

πŸ“š Description

This PR adds .jsx and .tsx to the list of extensions that are automatically resolved in the plugins 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 from ts to tsx.

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

  • I have linked an issue or discussion.
  • I have added tests (if possible).
  • I have updated the documentation accordingly.

Copy link

Review PR in StackBlitz Codeflow Run & review this pull request in StackBlitz Codeflow.

@toyi toyi changed the title feat(nuxt): allow plugins with .jsx or .tsx extensions feat(nuxt): allow auto-registration of plugins with .jsx or .tsx extensions Mar 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants