Alex Nordlund

That's absolutely correct, the repository mode is working exactly as intended as it lets you configure this This is covered in our FAQ https://github.com/node-gradle/gradle-node-plugin/blob/main/docs/faq.md#is-this-plugin-compatible-with-centralized-repositories-declaration

I feel like there's a 4th mode missing, but of the 3 that exists I find `FAIL_ON_PROJECT_REPOS` is the most appropriate setting, as all the others allow for sneaky issues...

Since caching is not enabled we can rule out Gradle writing to the directory And unless your subprojects are installing to the same `node_modules` we can rule out the plugin...

corepack looks to be distributed with all the current LTS versions, but also from what I can tell they're dropping it in the newest version (25) https://nodejs.org/dist/v25.2.0/docs/api/corepack.html Which is kinda...

It's a mistake that snuck in with a refactor, good catch!

This definitely sounds weird, and not something I'd expect to happen from a nodejs upgrade But first things first, why do you have both `npmInstall` and `npm_install`? Generally you only...

There's a bunch of things that could affect the time, but if you use a npm mirror that's close to your CI you should be able to speed up fetching...

Wouldn't the current `FooExecRunners` already work pretty well in a ValueSource? The current tasks are pretty much just thin wrappers around the runners, so it probably wouldn't be hard to...

Ah that'd do it, it's easy to simplify the construction of the ExecRunners, but types not accessible in ValueSources would make that problematic Adding my notes before I go to...

This looks to be similar to https://github.com/node-gradle/gradle-node-plugin/issues/334 which has a draft PR at https://github.com/node-gradle/gradle-node-plugin/pull/337