-
-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Parcel 1 does not work on Node v15 because it uses deasync #5294
Comments
I accidentally posted a new issue before realizing that it was a duplicate. Here is that issue's text:
|
This is an issue with the dependency deasync, probably missing binaries here: https://github.com/abbr/deasync-bin This isn't really a Parcel issue directly, we got rid of deasync in Parcel 2 for this reason as well as it not being totally reliable and slower than standard synchronous code. We can't easily get rid of it in Parcel 1 though as it would require a pretty large refactor. Hopefully we can release a stable Parcel 2 soonish. |
@DeMoorJasper / @john01dav - so is the solution here to downgrade Node for the interim? |
@m-w-d-d I just upgraded to Parcel 2. I didn't even need to change any of my code. |
@m-w-d-d you got 3 options really. Downgrade node, fix deasync or upgrade to parcel 2 |
@DeMoorJasper / @john01dav - I might have not realised Parcel 2 was out... ahem :) Thanks to you both! |
This is an issue with deasync and not parcel, in Parcel 2 we stopped using this as now there's a native way to do this in node... |
@vp2177 For my case the underlying problem was with |
π bug report
π Configuration (.babelrc, package.json, cli command)
Zero configs.
π€ Expected Behavior
π― Current Behavior
π Possible Solution
π¦ Context
π» Code Sample
π Your Environment
The text was updated successfully, but these errors were encountered: