Alex Nordlund
Alex Nordlund
This is related to #316
There hasn't been a commit or reaction in 8 months, if you're able to live without the Gulp and the Grunt parts of this I'd use the fork.
@alexvas do you need grunt/gulp in the plugin? Otherwise [node-gradle/gradle-node-plugin](https://github.com/node-gradle/gradle-node-plugin)
add `mavenLocal()` to your `buildscript.repositories` or `pluginManagement.repositories` (in settings.gradle) and build the plugin locally using `publishToMavenLocal` though you're going to need to switch to the fork to be able to...
The reason you're seeing this is because of https://github.com/srs/gradle-node-plugin/issues/336 The inputs are declared twice and the first part is not marked as optional, we've fixed this in the fork https://github.com/node-gradle/gradle-node-plugin
@mroloux this plugin hasn't seen active development in a long while, there's however a maintained fork available. But I also have a feeling that this wasn't an issue on Linux...
That's the one yeah, though for coloured output there might be a way to force yarn/npm to do coloured output. You could try adding `--color=full` into args and see if...
This issue has some variations that might be worth trying https://github.com/yarnpkg/yarn/issues/5733
Most tools do when the output isn't a tty, you can simulate it by doing `yarn install | cat`, but I'm glad you managed to get it working :-)
@nc-baku there's been no commits for the past 5 years, I recommend giving https://github.com/srs/gradle-node-plugin/issues/315 a read to get an idea on options