yarn.lock sometimes not created despite success Saved lockfile message

[jharris4]

Do you want to request a feature or report a bug?

bug

What is the current behavior?

yarn.lock is not created even though yarn cli reports that it was.

If the current behavior is a bug, please provide the steps to reproduce.

rm -rf node_modules
rm yarn.lock
yarn install
ls yarn.lock

What is the expected behavior?
The lock file should always be created

Please mention your node.js, yarn and operating system version.
MacOS 10.12.5
Node 8.0.0
Yarn 0.24.6

I've been seeing this issue intermittently for quite some time. Was sort of surprised to not (easily) find a duplicate issue. I'm pretty sure this is not related to Node 8 since I was seeing it intermittently with Node v7.

[jharris4]

ok, its happening much more frequently now. Perhaps it's aggravated by node 8 somehow.

[jharris4]

Here's the output from it just happening again. The first time, no lock file was generated but the second time it was.

$ yarn install
yarn install v0.24.6
info No lockfile found.
[1/4] 🔍  Resolving packages...
warning socket.io-client > socket.io-parser > isarray@2.0.1: Just use Array.isArray directly
[2/4] 🚚  Fetching packages...
[3/4] 🔗  Linking dependencies...
[4/4] 📃  Building fresh packages...
[1/3] ⠂ fsevents
[1/3] ⠄ fsevents
[2/3] ⠄ node-sass
[1/3] ⡀ fsevents
[1/3] ⠐ fsevents: node-pre-gyp http GET https://fsevents-binaries.s3-us-west-2.amazonaws.com/v1.1.1/fse-v1.1.1-node-v57-darwin-x64.tar.gz
[1/3] ⠠ fsevents: node-pre-gyp http GET https://fsevents-binaries.s3-us-west-2.amazonaws.com/v1.1.1/fse-v1.1.1-node-v57-darwin-x64.tar.gz
[2/3] ⠠ node-sass: Downloading binary from https://github.com/sass/node-sass/releases/download/v4.5.3/darwin-x64-57_binding.node
[3/3] ⠠ uws
[-/3] ⠠ waiting...
success Saved lockfile.
✨  Done in 22.18s.

$ yarn install
yarn install v0.24.6
info No lockfile found.
[1/4] 🔍  Resolving packages...
warning socket.io-client > socket.io-parser > isarray@2.0.1: Just use Array.isArray directly
[2/4] 🚚  Fetching packages...
[3/4] 🔗  Linking dependencies...
[4/4] 📃  Building fresh packages...
success Saved lockfile.
✨  Done in 25.60s.

[xmlking]

same thing for me here.
Node 8.0.0 and yarn v0.24.6
https://github.com/xmlking/hub/tree/master/server
I also have socket.io-client warning

[arcanis]

I haven't been able to reproduce it yet, and I've ran Yarn a lot of time :(

[jharris4]

It's happening on every project I am currently working with at least 50% of the time for me right now.

I don't know if it has any effect, but all the projects have some git dependencies of the style git+https://domain.com/r/repo.git#semver, and those git urls have their own dependencies in their respective package.json files.

[junosw]

Just had this start happening on a project I'm working on today. Same exact specs as @jharris4 :
MacOS 10.12.5
Node 8.0.0
Yarn 0.24.6

Can't get the yarn.lock to generate even though console output says it does. Additional piece of info - I discovered this issue when adding a new package and noticed that package.json was not being updated either.

[jharris4]

Just happened for me on a project without git dependencies, so definitely not related to that. Must be related to having upgraded to Node 8.

[junosw]

@jharris4 I suspect that is the case. I rolled back to 7.10 and it started working fine.

[jharris4]

Just tried with the newly released Node 8.1 and still having the issue.

[jharris4]

Just noticed that if node_modules are present, the lock file is reliably created. If node_modules are absent, the lock file is never properly created. I can reproduce this 100% of the time. Not sure how I can help someone else reproduce though.

[jharris4]

This bug has been driving me nuts, so I just finally put together a reliably reproducible example.

Copy the attached package.json.txt, file to an empty directory, rename it to package.json. Then do:
yarn install
yarn go

You should see a message in the console like this:

success Saved lockfile.
✨  Done in 21.93s.
NO LOCK FILE FOUND!!!
✨  Done in 23.47s.