Alex Nordlund

If you're ok with full version numbers in there you could use the same pattern as https://github.com/node-gradle/gradle-node-plugin/issues/232 `version` and `npmVersion` are both properties so they could be calculated from a...

This is a little tricky to implement right now since it lets you use versions like `16` and if you've got 16.13.1 installed locally you probably don't want it to...

Which `npm` version are you using? I don't see this in the documentation for 8.x and I'm not getting the warning on 8.5.0 either

The way yarn is being installed is through running pretty much `npm install --global --no-save --prefix yarn@yarnversion` This uses the `npm` bundled with your `nodejs` version in the case of...

Not happening for me with `8.15.0` ._. ``` root@628d2222b553:/test# npm --version 8.15.0 root@628d2222b553:/test# npm install --global --no-save --prefix prefixdir [email protected] added 1 package, and audited 202 packages in 4s 11...

Hi Lucas, Unfortunately this is [a current limitation in Gradle](https://docs.gradle.org/7.4.2/userguide/performance.html#parallel_execution)

When it comes to `package-lock.json` we have a tricky situation, with the current functionality the `npmInstall` task can be configured to run `npm ci` instead of `npm install` and in...

@belovaf sure, that'd be great! There's a branch called `test-sbs` where I've just been playing around with doing _slightly related_ work (the idea being to enable something like the [Toolchains...

Oh and if it requires dropping support for Gradle versions lower than `6.1` it'll have to wait until after the next release, but that's already being planned

Is that still true if `package.json` has changed but not `package-lock.json`? (which isn't necessarily the use-case we want to optimise for)