-
Notifications
You must be signed in to change notification settings - Fork 635
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
Nuxt 3.15 "Unexpected token" #2971
Comments
Facing similar issue after upgrading to Nuxt 3.15 which uses Vite 6 under the hood. |
I can also confirm this, that after upgrading to nuxt 3.15, I'm also getting |
I'll be investigating. It feels like this might be a core nuxt book. |
Getting the same error when running the dev server. Builds seem to work as expected. |
Oh yeah, this only happens in dev mode, |
@danielroe you have to insert u-modal or u-slideover components |
"I deleted the node_modules folder and reinstalled the dependencies, which fixed the issue. Previously, I was using Nuxt 3.12.0 and had used nuxi to upgrade. That might have been the cause of the problem." |
I think this might be a Vite (or esbuild) issue. The problematic file is |
I also encounter this error when I use UModal, USlideover, or UPopover. |
I also encountered this error: [nuxt] [request error] [unhandled] [500] Unexpected token ';' , when i try to install @nuxt/fonts package |
@danielroe Would you happen to have a temporary or emergency workaround available? |
As Daniel already mentioned, you can pin vite to v5. For example for pnpm:
|
I just reverted to Nuxt v3.14 and it worked, really want to try v3.15 w/ Vite 6 but maybe til it's resolved, we'll have to revert to v3.14 or with overrides solution |
Any fix in this using yarn same issue revert to Nuxt 3.14 "solves" issue but there are other issues with Nuxt 3.14 so any fix on this would be great asap. running Nuxt ui pro |
I also encounter this error when I use UDropdown. |
To everyone asking for a fix, there are two workarounds at the moment:
OR
When the issue is resolved upstream, you can remove the workaround. |
This comment has been minimized.
This comment has been minimized.
This is tracked upstream now via vitejs/vite#19096. This issue will be kept open - for visibility only - until the linked issue is resolved 👍🏻 |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
* Initial draft of dynamic lunchtime updating * Improve system message * Create a updateHours task * Working version of non-normal opening hour detection * Improve juvenes selector * Schedule updateHours task * Update deps * fix: updateHours task name * Move startup tasks to a nitro plugin * Move startup tasks to a nitro plugin * Increase AllContentLoaded timeout * Increase AllContentLoaded timeout * Add logging * Cleanup * Bind vite to v5 nuxt/ui#2971 * Finalize opening time style
This issue has been resolved in Vite 6.0.7 and you can refresh your lockfile to get the fix 👍🏻 @danielroe feel free to close this 😋 |
had this same problem, |
Please don't downgrade, just refresh your lockfile as Alex said. This was not a Nuxt issue and has been fixed in the latest Vite update, which you'll get that way. |
I have a similar issue.
|
@jonasfroeller this is a different issue. Please create a new issue with a reproduction :) |
It is my eslint configuration. Probably not a nuxt related issue.
|
All good now, thanks. |
Environment
Darwin
v20.10.0
3.15.0
3.17.2
2.10.4
npm@10.2.3
-
default
@vueuse/nuxt@12.2.0
,@nuxtjs/i18n@9.1.1
,@nuxt/ui@2.20.0
,@nuxt/fonts@0.10.3
,@hebilicious/authjs-nuxt@0.3.5
,@nuxt/icon@1.10.3
-
Version
v2.20.0
Reproduction
https://stackblitz.com/edit/nuxt-ui.
Description
Just upgraded my Nuxt version to 3.15, and I noticed that modal or slide over components for now are not working
they have updated the vite version, and I think this is the issue here.
Additional context
No response
Logs
The text was updated successfully, but these errors were encountered: