fix: do not traverse node_modules on wizard monitor for yarn

[lili2311]

• Ready for review
• Follows CONTRIBUTING rules
• Reviewed by Snyk internal team

What does this PR do?

Fixing a bug where if a yarn project is fixed with wizard we traversed the node modules via a specially set flag but then did not set this back just before monitoring.

While traversing node_modules for yarn is a must for now for patching (old style node_module traversal populates where each package lives on disk which is used during patch time) this fall back is not needed for yarn projects node > 6 when we run a test just before monitoring the project & sending the snapshot to snyk web.

Where should the reviewer start?

To replicate:

• clone https://github.com/lili2311/npm-lockfiles
• run snyk wizard in the yarn-lockfiles folder and see the error appear: not a node project (this is an error encountered because we are sending yarn.lock as a filename to the resolve-deps lib instead pf package.json)

[darscan]

I think wozard is my new favourite word :)

[lili2311]

Thanks I made it myself 🙄

[miiila]

🧙‍♂️

[snyksec]

🎉 This PR is included in version 1.103.2 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀