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.

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

unhandled exception with yarn v2 #13531

Closed
amirhosseinak20 opened this issue Dec 28, 2020 · 3 comments
Closed

unhandled exception with yarn v2 #13531

amirhosseinak20 opened this issue Dec 28, 2020 · 3 comments

Comments

@amirhosseinak20
Copy link

amirhosseinak20 commented Dec 28, 2020

Describe the bug
I was trying to implement storybook tutorial with yarn v2 and pnp, after i run yarn storybook or yarn run storybook i face this error
(node:96483) UnhandledPromiseRejectionWarning: Error: spawn ENOTDIR at ChildProcess.spawn (internal/child_process.js:407:11) at Object.spawn (child_process.js:553:9) at module.exports (/mnt/e/projects/ariana/iapp/.yarn/cache/open-npm-7.3.0-d582d8b42e-a212fc9cf6.zip/node_modules/open/index.js:152:34) at processTicksAndRejections (internal/process/task_queues.js:97:5) (node:96483) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict(see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 4984) (node:96483) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
Screenshot_20201228_170316

To Reproduce
to reproduce this issue you can clone this repo on branch new and run
yarn install yarn storybook

Expected behavior
Screenshot_20201228_172527

@merceyz
Copy link
Contributor

merceyz commented Dec 28, 2020

You need to unplug open by running yarn unplug open -AR

@amirhosseinak20
Copy link
Author

Thanks this solved my problem.
can you explain why this happened

@merceyz
Copy link
Contributor

merceyz commented Dec 29, 2020

open contains a native binary that is used on macOS but since native binaries can't be spawned within zip files it needs to be unplugged

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants