About min node version support

[fwh1990]

move-file@2.0.0: The engine "node" is incompatible with this module. Expected version ">=10.17".

It happened since you update dep cacache to version 15.0.3, because move-file is a dependency of cacache

[fwh1990]

The changelog say the min node version is 10.13.0，so I guess this is a bug

[alexander-akait]

Yep, unfortunately this is a transitive dependency and we can't fix it, package works on 10.13, just with a warning about experimental feature - fs.promises

[fwh1990]

npm/cacache#37

[fwh1990]

It's considered as an error and new deps can't be installed. I have to downgrade to 2.3.6

[alexander-akait]

@fwh1990 just update node@10 to latest version, it is always recommended to use latest version

[ccambournac]

@fwh1990 just update node@10 to latest version, it is always recommended to use latest version

Not so easy on our CI servers...

[alexander-akait]

Guys from npm teams always were very slow and often ignore problems

[ccambournac]

Guys from npm teams always were very slow and often ignore problems

Hi @evilebottnawi, what do you mean?

[alexander-akait]

@ccambournac cacache develop by npm team

[ccambournac]

@evilebottnawi
It seems like using yarn resolutions to force the use of move-file@1.2.0 allows latest terser-webpack-plugin to work with Node.js 10.16.2.

[alexander-akait]

@ccambournac I think it is time say npm team in twittier something...

[ccambournac]

twittier something

Should I laugh? :)

[alexander-akait]

@ccambournac Yep 😄

[ccambournac]

Sorry, I did not understand! 😄

[alexander-akait]

@ccambournac I meant that post via twitter to npm command will probably move this point from a dead spot

[ccambournac]

@evilebottnawi I don't really feel like twitting to npm team... :)

[fwh1990]

@evilebottnawi
It seems cacache@15.0.4 have fixed this problem by this commit: npm/cacache@bf88af0

[alexander-akait]

Will patch do release tomorrow

[ccambournac]

@evilebottnawi Everything now works as expected with the new release, thank you!

[fwh1990]

Sorry, I have not handle this issue for a few days, maybe jest-worker is facing the same problem:

jest-worker@26.0.0: The engine "node" is incompatible with this module. Expected version ">= 10.14.2". Got "10.13.0"

Shouldn't it be in devDependencies

[alexander-akait]

Oh, we still have a problem for jest-worker

/cc @SimenB It is possible to reduce node >= 10.13.0 for jest-worker?

[SimenB]

Yeah, probably. We have that version as a minimum in Jest since it includes nodejs/node#23206. That doesn't matter for jest-worker though, as it doesn't use the vm APIs, it's just easiest to use the same engines version for all packages. Can make an exception for jest-worker tho 👍

Could you open up an issue?

[alexander-akait]

@SimenB Big thanks! Let's open an issue. jest-worker is great project.

[alexander-akait]

Done jestjs/jest#10142

[fwh1990]

I suggest author append 10.13.0 to matrix.node-version in file .github/workflows/nodejs.yml, so that you can catch errors automatically before users upgrade it.