Alex Nordlund

@iamareebjamal issues are enabled now :-)

https://plugins.gradle.org/plugin/com.github.node-gradle.node - relocated plugin with a conditional fix for #299 now exists (since plugin portal does *not* handle snapshots)

Since development has picked up again I'll start backporting (forwardporting?) to `node-gradle`. As long as this repo is a one-man show I'll continue working on the node-gradle "community" fork. Which...

@srs maybe we should schedule a quick call some day and discuss the futures of these repositories?

I can't think of any major downsides of using the java plugin in a pure JavaScript project, so just apply that and you'll get sourceSets and all

This is one of the major features we've got in the fork [node-gradle/gradle-node-plugin/blob/master/docs/faq.md#how-do-i-use-npm-ci-instead-of-npm-install](https://github.com/node-gradle/gradle-node-plugin/blob/master/docs/faq.md#how-do-i-use-npm-ci-instead-of-npm-install)

You could create a `NpmTask` and have your `makeClients` be `finalizedBy` that

It's kinda amazing that you were able to use it on Gradle 6 as the latest version supported is Gradle 5, you can see https://github.com/srs/gradle-node-plugin/issues/315 for the background, but the...

Unfortunately this plugin isn't compatible with gradle 6, you can see https://github.com/srs/gradle-node-plugin/issues/315 for the full history. But there's a maintained fork of this plugin at https://github.com/node-gradle/gradle-node-plugin

The way that the plugin works is that it's using an `IvyRepository` to fetch a file, now the problem you're seeing is that in Gradle 5 and later you need...