Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

perf(nuxt): verbatim module syntax + restrict type discovery #23447

Merged
merged 1 commit into from Oct 2, 2023

Conversation

danielroe
Copy link
Member

πŸ”— Linked issue

❓ 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 avoids 'auto-discovery' or inclusion of all @types/ packages installed. It also enables verbatimModuleSyntax, which is important for <script setup> (see https://github.com/vuejs/tsconfig/blob/main/tsconfig.json#L30-L33).

πŸ“ Checklist

  • I have linked an issue or discussion.
  • I have updated the documentation accordingly.

@stackblitz
Copy link

stackblitz bot commented Sep 28, 2023

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

@danielroe danielroe changed the title perf(nuxt): restrict auto-discovered types + enable verbatim module syntax perf(nuxt): verbatim module syntax + restrict type discovery Oct 2, 2023
@danielroe danielroe merged commit 770d4c6 into main Oct 2, 2023
33 checks passed
@danielroe danielroe deleted the fix/tsconfig branch October 2, 2023 10:32
@github-actions github-actions bot mentioned this pull request Oct 2, 2023
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.

None yet

1 participant