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

Error on npm run dev #8

Closed
ruradium opened this issue Dec 16, 2022 · 6 comments · Fixed by #23
Closed

Error on npm run dev #8

ruradium opened this issue Dec 16, 2022 · 6 comments · Fixed by #23

Comments

@ruradium
Copy link

Project/riffusion-app/node_modules/next/dist/cli/next-dev.js:315
showAll: args["--show-all"] ?? false,
^

SyntaxError: Unexpected token '?'
at wrapSafe (internal/modules/cjs/loader.js:915:16)
at Module._compile (internal/modules/cjs/loader.js:963:27)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:1027:10)
at Module.load (internal/modules/cjs/loader.js:863:32)
at Function.Module._load (internal/modules/cjs/loader.js:708:14)
at Module.require (internal/modules/cjs/loader.js:887:19)
at require (internal/modules/cjs/helpers.js:74:18)
at Object.dev (/home/ray/Project/riffusion-app/node_modules/next/dist/lib/commands.js:10:30)
at Object. (/home/ray/Project/riffusion-app/node_modules/next/dist/bin/next:141:28)
at Module._compile (internal/modules/cjs/loader.js:999:30)

@hmartiro
Copy link
Member

Perhaps try a newer version of node? We're using v19.2.0

@TiagoTiago
Copy link

Perhaps try a newer version of node? We're using v19.2.0

There doesn't seem to be an update available on Linux Mint. Do I need to add some PPA for nodejs?

@chrisburrc
Copy link

I ran into the same issue on Linux Mint as well. It worked after updating nodejs to the latest stable version (18.12.1 at the time of writing).

I followed the instructions here. Use n module from npm in order to upgrade node:

sudo npm cache clean -f
sudo npm install -g n
sudo n stable

To upgrade to latest version (and not current stable) version, you can use

sudo n latest

@ruradium
Copy link
Author

fixed after upgrading to nodejs V18.x

@hmartiro
Copy link
Member

Thanks, adding a note to the readme about the node version.

@ayushnavtech
Copy link

Not fixed for me, I get this issue on docker, normally on terminal, it would run fine...

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

Successfully merging a pull request may close this issue.

5 participants