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
Do you want to request a feature or report a bug?
bug
What is the current behavior?
yarn install completes successfully but no yarn.lock is written and no "Saved lockfile" message is displayed.
yarn install
yarn.lock
If the current behavior is a bug, please provide the steps to reproduce.
Here is an example package.json:
Then run yarn install --ignore-scripts. This fails to generate a yarn.lock for me on both Ubuntu 16.04 and OSX.
yarn install --ignore-scripts
What is the expected behavior?
yarn.lock should be written
Please mention your node.js, yarn and operating system version.
yarn v0.27.5. Tried on both Ubuntu 16.04 and OSX. Also tried on both node 8.x and 6.x. Most recently trying on v6.11.1.
The text was updated successfully, but these errors were encountered:
Sorry for false alarm, I have found a --install.pure-lockfile true .yarnrc :(
--install.pure-lockfile true
.yarnrc
Sorry, something went wrong.
No branches or pull requests
Do you want to request a feature or report a bug?
bug
What is the current behavior?
yarn install
completes successfully but noyarn.lock
is written and no "Saved lockfile" message is displayed.If the current behavior is a bug, please provide the steps to reproduce.
Here is an example package.json:
Then run
yarn install --ignore-scripts
. This fails to generate ayarn.lock
for me on both Ubuntu 16.04 and OSX.What is the expected behavior?
yarn.lock should be written
Please mention your node.js, yarn and operating system version.
yarn v0.27.5. Tried on both Ubuntu 16.04 and OSX. Also tried on both node 8.x and 6.x. Most recently trying on v6.11.1.
The text was updated successfully, but these errors were encountered: