GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
npm@2 didn't emit these and to be honest, it's not that interesting. The test change actually just reverts a previous test change when these warnings were introduced.
This will half fix #9113
add (or verify exists) a test that DOES trigger an error at the bottom from a top level package. Invalid package.json.
Reviewed by me via ScreenHero, with the suggestion of adding a sad path test. 🐑 once that's added.
ls: Elminate warnings about missing package.json at top level
Elminate warnings about missing package.json at top level
Landed as 02420dc. It's fitting that these trees are getting "elminated"! Thanks, Rebecca!