gradle-node-plugin icon indicating copy to clipboard operation
gradle-node-plugin copied to clipboard

Gradle plugin for integrating NodeJS in your build. :rocket:

Results 96 gradle-node-plugin issues
Sort by recently updated
recently updated
newest added

We should probably publish the snapshots somewhere like JCenter. This is related to #15 and #10

When I set `nodeModulesDir = file("${project.buildDir}")` in my `build.gradle` the `node_modules` folder still ends up in `${projectDir}` and not `${project.buildDir}`.

Is it possible to use the node version with V8 canary and how can I do it? The problem that I see is that repository pattern is different: https://nodejs.org/download/v8-canary/ I...

I suggested to Gradle some API improvements to fix issues I encountered when integrating lazy configuration in the plugin code in gradle/gradle#12974. @big-guy made a kind of code review of...

I'm trying to set up a multi-project Gradle build. We have a node (Angular) library, several Angular projects that depend on the library, and Spring Boot (Java) projects that will...

I tried using below two node plugins in my gradle build - `id "com.moowork.node" version "1.3.1" ` and ` id "com.github.node-gradle.node" version "2.2.1" ` and this is how my gradle...

workaround exists

Right now I have the following ``` node { version = '10.16.3' download = true } ``` I would like to pin to https://nodejs.org/dist/latest-v10.x ``` node { version = 'latest-v10.x'...

enhancement
workaround exists

Right now gradle-node-plugin ignores gradle offline mode and contacts the registry anyway. The expected behavior is that it uses the local node_modules and perhaps using the npm offline flag. It...

enhancement

Currently, the `YarnInstallTask` outputs contain the whole `node_modules` directory - https://github.com/node-gradle/gradle-node-plugin/blob/master/src/main/groovy/com/moowork/gradle/node/yarn/YarnInstallTask.groovy#L55 I wonder if anyone really gets benefit out of this - it takes a really long time for Gradle...

On some dev machines, under totally strange circumstances this kicks builds using node-gradle/gradle-node-plugin : https://github.com/yarnpkg/yarn/issues/7584 current workaround for this is to run `sh gradlew yarn_cache_clean` maybe sth else could be...

workaround exists