-
Notifications
You must be signed in to change notification settings - Fork 571
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
engine.io package installation with yarn causes yarn.lock to not be created #516
Comments
This seems to be specific to the use of optionalDependencies section in package.json. I've filed a new issue in the yarn repro. yarnpkg/yarn#3728 This issue can probably be closed, since it seems to be a bug in yarn. I only filed it here in case anyone else stumbles onto the same issue. :-) |
It's actually the |
If/when that gets merged, I can confirm that it's fixed, and then it'd be great to update the |
Fixes socketio#536 Fixes socketio#516 Fixes socketio#474
Related: - socketio/socket.io#2956 - socketio/socket.io#3100 Fixes #536 Fixes #516 Fixes #474
uws is not deployed to or in any way supposed to work with Yarn. uws supports Node.js and NPM, nothing else. If you still insist on using it in environments where it is not intended to work then that's your issue. |
Note: for support questions, please use one of these channels: stackoverflow or slack
You want to:
Current behaviour
When installing engine.io 3.1.0 with yarn, the yarn.lock file is not created despite yarn saying it was.
Steps to reproduce (if the current behaviour is a bug)
Create a package.json with the following content (only dependencies are important):
then run
yarn install
Expected behaviour
yarn.lock file should be properly created. Yarn says it was, but the
yarn.lock
file does not actually exist.Setup
Other information (e.g. stacktraces, related issues, suggestions how to fix)
This is consistently reproducible with Node 8.x, Yarn 0.24.6 and MacOS 10.12.5.
Note that the bug only reliably happens on first install (
rm -rf node_modules
andrm yarn.lock
)This bug was originally filed on yarn: yarnpkg/yarn#3555
The text was updated successfully, but these errors were encountered: