Alex Nordlund
Alex Nordlund
I think the current setup in the PR looks good, it's backwards-compatible and we can document what to do in the `README` If someone is intentionally setting the tag to...
@roobre I think your rebase accidentally caught the wrong change
How did the build fail? I can't think of anything that should break
The problem is (or at least should be) Gradle 6.x, not the node version, you can see #315 for more information about the issue. There's multiple issues/PRs about the lack...
The fork should work fine without any workarounds, I don't think you need to import `YarnTask` to get this to work, simply changing to `id("com.github.node-gradle.node") version "2.2.1"` should be fine
There's currently no support for it, but it could be written using https://docs.gradle.org/current/userguide/custom_tasks.html#sec:declaring_and_using_command_line_options
If you use the preconfigured yarn install task from the fork I think it should work out-of-the-box
I don't think this is an issue with the plugin, it seems to be specific for npm. The plugin just sends the arguments, if npm ignores them it won't matter...
Are you using the latest version? We have a community fork at https://github.com/node-gradle/gradle-node-plugin but iirc a project at work was using that successfully before switching to the fork
Since there doesn't seem to be anything happening here I forked it to https://github.com/node-gradle/gradle-node-plugin and started relocating the plugin, I mostly did this since I need #299 fixed but I...