We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
yalc.lock entry:
"@what/ever": { "signature": "012344568987987", "file": true, "pure": false },
Will be replaced with "pure": true when @what/ever is yalc push because of the line: https://github.com/whitecolor/yalc/blob/30d0cc7c933c41b71e578244b07538acae1085d6/src/update.ts#L54
"pure": true
yalc push
Does not respect yalc.lock configuration at all, but unpreventably forces the --pure default via subsequent:
https://github.com/whitecolor/yalc/blob/30d0cc7c933c41b71e578244b07538acae1085d6/src/add.ts#L116
Says to use --no-pure, but --no-pure can't be given to yalc push, and earlier yalc add --no-pure is not respected.
yalc add --no-pure
The text was updated successfully, but these errors were encountered:
That is a major problem for us - we always need to remove the line by hand.
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
yalc.lock entry:
Will be replaced with
"pure": true
when @what/ever isyalc push
because of the line:https://github.com/whitecolor/yalc/blob/30d0cc7c933c41b71e578244b07538acae1085d6/src/update.ts#L54
Does not respect yalc.lock configuration at all, but unpreventably forces the --pure default via subsequent:
https://github.com/whitecolor/yalc/blob/30d0cc7c933c41b71e578244b07538acae1085d6/src/add.ts#L116
Says to use --no-pure, but --no-pure can't be given to
yalc push
, and earlieryalc add --no-pure
is not respected.The text was updated successfully, but these errors were encountered: