Alex Nordlund
Alex Nordlund
This is one of the reasons why we created the fork https://github.com/node-gradle/gradle-node-plugin/issues/2
The gulp plugin consists of an `npm install gulp` and a Node Task pointing to the `node_modules/bin/gulp.js` Personally I think you'd be better off using the newly introduced NpxTask for...
I'm pretty sure we solved this a long time ago in the fork
Well it's working flawlessly in our examples, so maybe you can create a small repository showing the issue and posting it in the fork's issues?
> I'm having lots of similar issues for days now. it has something to do with mooworks conflicts I think., or kotlinNodeJsSetup or resources folders. No matter what I do...
There's an actively maintained fork at https://github.com/node-gradle/gradle-node-plugin But we've dropped the grunt/gulp support in favor of npx
If you're still on gradle 2 you have great incentives to upgrade, it's a pretty painless process and gradle gets *much* faster
That kinda makes me curious about your fork as this issue comes with gradle 4 or 3
Also, in the case of `npm install` the `package-lock.json` should probably be an **output** https://docs.npmjs.com/files/package-lock.json
I think either solution should work ```global.redis.password | Global Redis® password (overrides auth.password)```