-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
node12.16.0 Operation error #8644
Comments
Does cesium plan to support the new version of nodejs? |
@ShareQiu1994 thanks for opening an issue. Cesium already supports Node 12 and I am unable to reproduce this problem with 12.6.0. Can you please provide the exact steps to recreate it? It appears Node 12.6.0 has 6 significant regressions that they quickly patched in 12.6.1: https://github.com/nodejs/node/blob/master/doc/changelogs/CHANGELOG_V12.md#2020-02-18-version-12161-erbium-lts-mylesborins Perhaps you are hitting one of these? |
@mramato Thank you for your answer. repro steps: My environment: When I upgraded the node to 12.16.1, I found that the problem still existed. |
@ShareQiu1994 My apologize but I can now reproduce this. I accidentally ran with 12.6 instead of 12.16. This is a breaking change during the 12.x line from the NodeJS team. Looks like they changed behavior as of 12.10. I'm looking into it. |
There are 3 issues here:
1 is a showstopper for 1.67, 2 is a showstopper for 1.68, and 3 is stuck waiting on other third party dependencies to update to Node 12. |
Updated my above comment but I'm closing this issue in favor of tracking it as part of #8452 |
@mramato Thank you for your efforts, I will continue to pay attention to its changes |
This is fixed in master and will be released as part of 1.68 on April 1st. |
I'm using nodejs 12.16.0 and cesium 1.66
In node 12.16.0, I found that cesium couldn't run:
When I switch to node 10.17.0, cesium 1.66 can run
The text was updated successfully, but these errors were encountered: