SyntaxError: Unexpected token '?'

[frakkio]

I'm trying to add @nuxt/image to my project using yarn node version is v12.22.1, nuxt version 2.15.8
and I got these errors:

ERROR  [@nuxt/image] ipx is an optional dependency for local image optimization and is not properly installed. 
Please try npm install or yarn install again.
FATAL  SyntaxError: Unexpected token '?'
 at node_modules/@nuxt/image/dist/module.js:130:13
 at async Object.ipxSetup [as setup] (node_modules/@nuxt/image/dist/module.js:128:48)
 at async ModuleContainer.imageModule2 (node_modules/@nuxt/image/dist/module.js:270:7)
 at async ModuleContainer.addModule (node_modules/@nuxt/core/dist/core.js:239:20)
 at async ModuleContainer.ready (node_modules/@nuxt/core/dist/core.js:55:5)
 at async Nuxt._init (node_modules/@nuxt/core/dist/core.js:478:5)

  │   ✖ Nuxt Fatal Error                         
  │
  │   Error: SyntaxError: Unexpected token '?'   

error Command failed with exit code 1.

I've also tried to add ipx with the same results

[stmoerman]

Same issue here on nuxt 2.15.7 and node v16.13.0 - not sure why it's requiring this dependency or not properly installing it.

For now I found that downgrading @nuxt/image to 0.6.0 fixed this for me.

[comfuture]

same here.
It works properly on @nuxt/image@0.6.0, and ipx@0.9.1.
npm audit fix command will upgrade @nuxt/image to 0.6.1 so be careful.

[Tragio]

I have the same problem, but not happening locally, only when building on Vercel. Downgrading from 0.6.2 to 0.6.0 fixed the problem.

[memotux]

Confirm issue @nuxt/image@0.6.2.

Downgrading to @nuxt/image@0.6.0 work.

[weotch]

Had this issue when deploying to Netlify using --target=static on 0.6.2. Switching to 0.6.0 worked for me as well.

[kezek]

Having the same issue.

[snakemastr]

Same, breaks on production build because we use npm audit fix in our build process.
I am not sure what the correct solution is here, probably will create the responsive images manually as there are not as much yet..

Is this problem caused by Nuxt 2 dragging its feet towards Nuxt 3 and therefore unable to fully support optional chaining (probably due to outdated packages like webpack 4)?

[speker2010]

This error caused by using ?? in ipx: https://github.com/unjs/ipx/blob/9296aa2e0fb376f8f18824f1306a9998b8a39a98/src/utils.ts#L4

If I replace ?? with ||, the error occurs in (reqOptions?):
https://github.com/unjs/ipx/blob/9296aa2e0fb376f8f18824f1306a9998b8a39a98/src/sources/http.ts#L27

Nuxt runs without errors, if I remove the optional operator.

[speker2010]

Updating node v12 to v14 helped me

[pi0]

Please use Node.js >= 14 (16 LTS)

[kumaresaninfo]

Same error i am getting, after node js version upgrade

Node Version :- v18.19.1

I need solution

[hieult-hybrid-technologies]

Same error i am getting, after node js version upgrade

Node Version :- v18.19.1

I need solution

did u fixed?