-
Notifications
You must be signed in to change notification settings - Fork 210
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
NPM run tasks with pre and/or post do not properly run #146
Milestone
Comments
+1 |
It rather defeats some of the purpose of this plugin, but you can do something like:
Essentially, use the plugin to install node and run the npm install, then just run the usual npm scripts with npm as a normal executable. |
We were able to make it work by using a local 'npm' installation. In our case:
|
I could not solve it by just using the above configuration. Though I spotted the reason of this issue described in #164 |
s0x
added a commit
to s0x/gradle-node-plugin
that referenced
this issue
Dec 19, 2016
hjeong11
pushed a commit
to tacitknowledge/gradle-grails-sass
that referenced
this issue
Jul 6, 2017
hjeong11
pushed a commit
to tacitknowledge/gradle-grails-jspm
that referenced
this issue
Jul 6, 2017
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
Hi,
As we started to use more NPM scripts with version 2.12, we've noticed some issues for this task:
In package.json we have the following scripts:
When running npm run e2e from command line, it properly. That is it runs pree2e script and then the e2e one.
When doing the same through the Gradle task above, it shows on the console the following commands:
But the commands do not actually execute (no-op for both). I wonder if the blame is on the the way the gradle plugin runs NPM with npm_cli.js
Considering NPM scripts is becoming a prominent way of building web apps, it would be good if we can have some more tests/support to NPM run.
Thanks for a great plugin, by the way.
The text was updated successfully, but these errors were encountered: