Skip to content
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.

Sign up for GitHub

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

Jump to bottom

frozen-lockfile does not fail when lockfile is autocorrected because of incorrect entries #3420

Closed
victornoel opened this issue May 16, 2017 · 2 comments
Closed

frozen-lockfile does not fail when lockfile is autocorrected because of incorrect entries #3420

victornoel opened this issue May 16, 2017 · 2 comments
Labels
triaged

Comments

@victornoel
Copy link
Contributor

Since #3106, yarn autocorrect the lockfile in some cases.

I was expecting that using --frozen-lockfile would fail in that case, since it means modifying the lockfile.

I suppose that check should fail too, as well as --pure-lockfile…
@victornoel
Copy link
Contributor Author

By the way, there is a typo (ignoring) in the warning message:

warning Lockfile has incorrect entry for "typescript@>=2.0.0 <2.3.0". Ingoring it.

@bestander
Copy link
Member

duplicate #3313

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
triaged
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@victornoel @bestander