frontend-maven-plugin: npm WARN generates a Maven ERROR

In my npm install phase some node_modules generate some warnings about deprecated versions (like grunt). But in the Maven log, this is an ERROR instead of a WARNING. We’re using Jenkins as our build tool and these errors cause wrong log analysis.

[INFO] --- frontend-maven-plugin:0.0.27:npm (install node, npm and dependencies) @ theme ---
[INFO] Found proxies: []
[INFO] Running 'npm install --color=false' in C:\theme
[ERROR] npm WARN deprecated lodash@0.9.2: lodash@<2.0.0 is no longer maintained. Upgrade to lodash@^3.0.0
[ERROR] npm WARN deprecated lodash@1.0.2: lodash@<2.0.0 is no longer maintained. Upgrade to lodash@^3.0.0
[ERROR] npm WARN deprecated npmconf@2.1.2: this package has been reintegrated into npm and is now out of date with respect to npm
[ERROR] npm WARN prefer global node-gyp@3.2.1 should be installed with -g

Changing the logging from ERROR to WARNING would be nice.

About this issue

Original URL
State: closed
Created 8 years ago
Comments: 20 (6 by maintainers)

Commits related to this issue

Fixes #41 #343 rewrites ProcessExecutor using commons-exec By using commons-exec instead of ProcessBuilder we can support killing the Node process if the Maven build is stopped. An optional timeout c... — committed to tjuerge/frontend-maven-plugin by tjuerge 8 years ago
Merge pull request #380 from mriehema/fix-343 Fix #343 — committed to eirslett/frontend-maven-plugin by eirslett 8 years ago

Most upvoted comments

Even with the --verbose flag too, I do not see any additional error messages:

[WARNING] npm WARN sample-typescript-project@1.0.0 No repository field.
[WARNING] npm WARN sample-typescript-project@1.0.0 No license field.
[ERROR]
[INFO] added 806 packages in 379.959s

Also, tried to with -X command to see if maven prints any additional log messages, still do not really see anything in particular.

Is the plugin reporting this [ERROR], which is causing our CI to break? @eirslett @mriehema

pritish-devurkar on Aug 28, 2017