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

tsx and i18n conflict, parsing error #3383

Open
yveeven opened this issue Mar 1, 2025 · 1 comment
Open

tsx and i18n conflict, parsing error #3383

yveeven opened this issue Mar 1, 2025 · 1 comment

Comments

@yveeven
Copy link

yveeven commented Mar 1, 2025

Environment

  1. codesandbox

  • Operating System: Linux
  • Node Version: v20.12.0
  • Nuxt Version: 3.15.4
  • CLI Version: 3.22.2
  • Nitro Version: 2.10.4
  • Package Manager: [email protected]
  • Builder: -
  • User Config: future, compatibilityDate, devtools, modules
  • Runtime Modules: @nuxtjs/[email protected]
  • Build Modules: -

  1. stackbiltz

  • Operating System: Linux
  • Node Version: v18.20.3
  • Nuxt Version: 3.15.4
  • CLI Version: 3.22.2
  • Nitro Version: 2.10.4
  • Package Manager: [email protected]
  • Builder: -
  • User Config: future, compatibilityDate, devtools, modules
  • Runtime Modules: @nuxtjs/[email protected]
  • Build Modules: -

Reproduction

  1. codesandbox: https://codesandbox.io/p/devbox/7yl7mz
  2. stackbiltz: https://stackblitz.com/edit/nuxt-starter-xaag2xvm

Describe the bug

When the project has an i18n dependency, the tsx code cannot be written correctly in'SFC <script setup lang = "tsx">, and an error is reported:

ERROR  Pre-transform error: ',' expected.                                                                                                                                                                         
  Plugin: unplugin-vue-i18n:directive
  File: /Users/yveeven/pm/temp/app/app.vue

Additional context

But I got different results in codesandbox and stackbiltz using the same code, stackbiltz is up and running

Logs

@yveeven
Copy link
Author

yveeven commented Mar 2, 2025

#3208 Resolved

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant