Invalid node version

[paleite]

I couldn't install terser because of a version mismatch. I think the trailing comma after each version may be causing the issue:

terser/package.json

Line 9 in 571fd99

"node": "^10.0.0,^11.0.0,^12.0.0,>=14.0.0"

I think it should be space-separated

[paleite]

PR #859

[tomaszs]

Same here:

error terser@5.3.6: The engine "node" is incompatible with this module. Expected version "^10.0.0,^11.0.0,^12.0.0,>=14.0.0". Got "1

Installed version:

14.13.1

[harshitsilly]

same here

[LoaderB0T]

duplicate #854

[ycjcl868]

+1

[ghost]

+1

[Nelosen]

+1

[CarlosAzocar]

+1

[dmoosocool]

+1

terser@5.3.6: The engine "node" is incompatible with this module. Expected version "^10.0.0,^11.0.0,^12.0.0,>=14.0.0". Got "13.13.0"

Installed version:

13.13.0 14.7.0 14.14.0 

[akryll]

+1
error terser@5.3.6: The engine "node" is incompatible with this module. Expected version "^10.0.0,^11.0.0,^12.0.0,>=14.0.0". Got "12.19.0"

[dolmira]

+1

[WildXav]

+1

[coderrorer]

+1

[s-dupuis]

+1

error terser@5.3.6: The engine "node" is incompatible with this module. Expected version "^10.0.0,^11.0.0,^12.0.0,>=14.0.0". Got "14.14.0"

[anachronic]

here's a temporary workaround for y'all

[jodybrewster]

here's a temporary workaround for y'all

That works, big thanks!

[ipeshev]

+1
adding you to my own npm blacklist

[akryll]

here's a temporary workaround for y'all

That works, big thanks!

Lol, screw this into my company's deployment with a wagon of approvals and signatures

[alxkat]

+1

[dev7ch]

+1000 ;)

[ollwenjones]

Anybody know why this happens when yarn.lock should be enforcing the same versions of everything? I wouldn't have expected to see this breakage unless someone at my org upgraded something on our project.

[mattvb91]

@ollwenjones yarn lock is only enforced if you use yarn --frozen-lockfile its not enabled by default

[ollwenjones]

@mattvb91 it is 100% enabled in our build scripts though. this got past it. unless it's the combination of --frozen-lockfile and --force ?

[mattvb91]

@ollwenjones puuuh not sure, we have also been struggling with both npm's and yarns locking mechanism for the past year

[ollwenjones]

@mattvb91 Looks like there's a known issue with --frozen-lockfile and --force flags at the same time.
yarnpkg/yarn#5215 This is how it happened in our environment, in case anyone else hits the same thing.

[GThairi]

+1

[fabiosantoscode]

Hey there! This is now fixed in 5.3.7.

[sclausen]

Hey there! This is now fixed in 5.3.7.

So it's correct, that 5.3.7 is incompatible with node 13?

[fabiosantoscode]

That is correct. Terser on node 13 works fine when require()d but it's not supported due to a large amount of ESM bugs stopping it from being imported.

[ljharb]

@fabiosantoscode id be happy to make a PR fixing your exports field to work on every v13 version, if you’re interested (it’s a small change; i recently did the same for yargs)

[fabiosantoscode]

Hey there @ljharb!

If you can do it while maintaining support for the other versions, I would appreciate it!

[ljharb]

Absolutely; PR incoming.

[ljharb]

#861