fix: issue #7892 - fix for npm install creating directories and empty package.json file

[Kyle-Ignis]

fix for npm install creating directories and empty package.json file when accidentally run in the wrong directory in a project.

References

Fixes #7892

[Kyle-Ignis]

ready for review, likely will need some updates.

[wraithgar]

While this does appear to fix the immediate problem, it does so in a pretty heavy-handed way. Typically we don't want to add single-use lib files to npm. If code needs to be shared between commands that's usually a signal that the code belongs elsewhere. Also, we tend not to add new unit tests. All new tests should interact with npm at the highest level possible, right now that means the mock-npm in tests. If this ends up in arborist it would need to go into the appropriate test and interact w/ arborist directly, not this new code in isolation.

This likely is something that applies to all arborist commands. Off the top of my head I know that npm update isn't accounted for here, but it would need to be.

The fix for this probably needs to live in arborist itself. That's the package that "owns" this process.

[Kyle-Ignis]

Thank you for the guidance. I will take another stab at this from that route. Hopefully we can get this fixed and solve this issue.