bripkens / admin Goto Github PK

https://lernajs.io/ would make releases a lot easier

It quite frequently happens that Node.js dependencies are installed wrongly. Dependencies requiring native compilation should be marked as offline so that installation becomes a non-critical error.

On admin startup, this case should be logged and the UI should contain a note explaining what is wrong.

Version 1.13.2 of prettier was just published.

This version is covered by your current version range and after updating it in your project the build failed.

prettier is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

Version 4.1.0 of pino just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As pino is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

We really need a good testing story…

In the underlying version of V8 in Node 12 the deprecated v8::Handle was removed. In the profile plugin the @risingstack/v8-profile still depends on it.
For the use of node 12 an update or an alternative like v8-profiler-next is necessary.

https://github.com/TomFrost/node-vitalsigns

Maybe in the style of the Grunt logo?

Version 1.14.8 of nodemon was just published.

This version is covered by your current version range and after updating it in your project the build failed.

nodemon is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴