Replies: 2 comments 1 reply
|
Are there any cons? Basically, can people still run |
1 reply
|
The only downside I'd see is that you need to have the dependencies on your disk twice, since gradle just gets its own version of npm which in turn gets all the dependencies. If you set up an environment for development, you'll have all of them in another place anyway. Since nobody needs to use gradle in this case though, this is not a reason not to have it. So 👍 from my side. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
What are your thoughts about introducing gradle as build tool on top of npm?
With the gradle npm plugin, the build process' dependencies could be reduced to only rely on the gradle wrapper. In contrast to the current system, where nodejs / npm has to be installed.
These pros have fueled this thought:
All reactions