listr2 unexpected token '??='

[Marckon]

Description

after update from v13.2.3 to v13.3.0, when run in husky pre-commit hook I get this error:

file:///xxxx/node_modules/_listr2@6.6.1@listr2/dist/index.js:206
    this.options.fields ??= {};
                        ^^^

SyntaxError: Unexpected token '??='
    at Loader.moduleStrategy (internal/modules/esm/translators.js:149:18)
husky - pre-commit hook exited with code 1 (error)

Steps to reproduce

Debug Logs

expand to view

COPY THE DEBUG LOGS HERE

Environment

node v18.4.0
package.json

"lint-staged": {
    "*.{js,jsx,ts,tsx}": "eslint"
  },

• OS:
• Node.js:
• lint-staged:

[iiroj]

13.3.0 was an incorrect release and is functionally the same as 14.0.0. Please upgrade to that.

[iiroj]

See #1312 for more info.

[iiroj]

That said, the nullish coalescing assignment should be available since Node.js 15... are you using 14 by accident?

[Marckon]

Thanks! Indeed, I accidentally used v14 node. I configured install-node in my package.json file, although node -v outputs the v18.4.0 version

  "engines": {
    "install-node": "v14.17.5"
  },

[iiroj]

Relevant PR is #1289