-
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
Error using cesium in Node 12 or 13 #8452
Comments
FYI, a ton of projects are affected by this change in NodeJS. even |
This appears to be related to gulp not working in Node 13 either. I changed it to high and will write up a gulp issue (since I don't see one) and link to it from here. |
This appears to be affecting Node 12 now as well. |
This is now a major issue because most users are migrating to Node 12. While I don't think it's something we can hurry up and fix in today's release, we absolutely need to address it for 1.68 on April 1 so I updated the tag. |
There are actually two issues here:
2 is a showstopper for 1.68, 3 may be fixable once we address 2 but it may be blocked by third part dependencies (jsDoc). |
This is fixed in master and will be released as part of 1.68 on April 1st. |
The cesium node module does not work in Node 13 due to the upgrade to ES6 modules and a breaking change in Node. The error message looks something like:
We've seen this issue in obj2gltf and gltf-pipeline:
CesiumGS/gltf-pipeline#507
CesiumGS/obj2gltf#225
@mramato has some ideas for fixing this before the Jan 2 release.
The text was updated successfully, but these errors were encountered: