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

Unexpected token '||=' #15348

Closed
zachdyer opened this issue Nov 4, 2022 · 5 comments
Closed

Unexpected token '||=' #15348

zachdyer opened this issue Nov 4, 2022 · 5 comments

Comments

@zachdyer
Copy link

zachdyer commented Nov 4, 2022

Environment


  • Operating System: Windows_NT
  • Node Version: v14.16.0
  • Nuxt Version: 3.0.0-rc.12
  • Nitro Version: 0.6.1
  • Package Manager: npm@6.14.11
  • Builder: vite
  • User Config: -
  • Runtime Modules: -
  • Build Modules: -

Reproduction

npx nuxi init .
npm install
npm run dev

Describe the bug

When you visit localhost:3000 you get the error.

Additional context

No response

Logs

Unexpected token '||='

at new Script (vm.js:101:7)
at createScript (vm.js:262:10)
at Object.runInThisContext (vm.js:310:10)
at ViteNodeRunner.directRequest (/C:/Users/zachd/OneDrive/Documents/GitHub/nuxt3/node_modules/vite-node/dist/client.mjs:245:19)
at processTicksAndRejections (internal/process/task_queues.js:93:5)
at async ViteNodeRunner.cachedRequest (/C:/Users/zachd/OneDrive/Documents/GitHub/nuxt3/node_modules/vite-node/dist/client.mjs:129:12)
at async request (/C:/Users/zachd/OneDrive/Documents/GitHub/nuxt3/node_modules/vite-node/dist/client.mjs:152:16)
at async C:/Users/zachd/OneDrive/Documents/GitHub/nuxt3/node_modules/nuxt/dist/app/composables/index.mjs:46:31
at async ViteNodeRunner.directRequest (/C:/Users/zachd/OneDrive/Documents/GitHub/nuxt3/node_modules/vite-node/dist/client.mjs:250:5)
at async ViteNodeRunner.cachedRequest (/C:/Users/zachd/OneDrive/Documents/GitHub/nuxt3/node_modules/vite-node/dist/client.mjs:129:12)
@dargmuesli
Copy link
Member

I saw this error a few hours ago too while tracing another issue. It would surely help if you could provide a minimal reproduction! 🙌

@lawrence-V
Copy link

I have the same issue.

@manniL
Copy link
Member

manniL commented Nov 4, 2022

Hey! This should be resolved when using edge channel, or in the upcoming RC via nuxt/framework#8299

@manniL manniL closed this as not planned Won't fix, can't repro, duplicate, stale Nov 4, 2022
@zachdyer
Copy link
Author

zachdyer commented Nov 4, 2022

Maybe it has something to do with it running on Windows.

@manniL
Copy link
Member

manniL commented Nov 4, 2022

It has been resolved in RC.13 and was related logical assignments not being supported in some Node versions.

@danielroe danielroe added the 3.x label Jan 19, 2023
@danielroe danielroe transferred this issue from nuxt/framework Jan 19, 2023
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

5 participants