-
Notifications
You must be signed in to change notification settings - Fork 552
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: Pass down strict out of sync flag to the lockfile parser #369
Conversation
18fe20d
to
8099cc9
Compare
568322f
to
c664888
Compare
LGTM |
c664888
to
06379db
Compare
42a8fda
to
42b1ec1
Compare
🎉 This PR is included in version 1.134.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Hmm, it doesn't seem to work for me 🤔 It happens mainly for our yarn workspace local dependencies but I was able to reproduce it on the simplest project possible, too. Let's say we have
Then, let's run Add any dependency (let's say
Am I doing something wrong? |
👋 Could you please share your |
I followed the steps you provided:
When running |
Thanks for quick response @lili2311 🙌 |
What does this PR do?
Allow users to disable strict out of sync by passing it as a flag, the default lockfile based project testing behaviour is strict mode of CLI. It is problematic for repos that use yarn workspaces or link to deps in the same repo.
Where should the reviewer start?
Tests
How should this be manually tested?
snyk test --strictOutOfSync=false
on a project that is out of sync (make it out of sync by manually adding a dep to package.json and not re-locking the deps)