$ npm install
└── UNMET PEER DEPENDENCY request@^2.74.0
npm WARN email@example.com requires a peer of request@^2.74.0 but none was installed.
It looks like I've found a way to exit with
1, after/before (I think the order doesn't matter) doing the general
npm install I need to run
npm install my_module which will exit with
1. That means I can define a list of modules I want to make sure to have exactly what they need (defined in
peerDependencies) in my CI script, not pretty but it's better than nothing.
npm install doesn't break no matter what kind of dependencies nonsense you will define in your
npm install module_name will break if you have nonsense in your