-
Notifications
You must be signed in to change notification settings - Fork 250
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
ES module error on Node.js 13 #507
Comments
Looks like the same issue in @mramato do you know the best way to fix this? |
This actually looks like a breaking change introduced in Node 13, everything works on 10 and 12. I'll have to do a little research to figure out the right path forward. @lilleyse can you write up an issue in Cesium about Node 13 support and link the other two issues? Tag it |
Here's the cesium issue: CesiumGS/cesium#8452 |
I get this warning also in node v12.13.1:
|
I solved this issue by running node v12.0.0 |
Do anyone worked on this problem ? Changing node version of the project is not a solution ! As noticed by @md2perpe the problem also exists in some version of Node v12 so it is not v13 only related. |
@AlexPiro there's a PR into Cesium to fix this that should go out with it's next release: CesiumGS/cesium#8659 (April 1) We just need to do some additional review/testing on it. |
If I try converting a glb to draco using node v12.0.0 I get |
@edsilv you might need to run |
CesiumJS 1.68.0 was released yesterday with the fix. I tested that gltf-pipeline now works with Node 13.12.0. |
When running the tests using node v13.3.0 the following error is thrown.
It seems like an error due to Cesium's recent upgrade to using ES6 modules in v1.63, as manually setting the package to v1.62.0 causes the tests to run successfully.
In Node versions 12 and below this error doesn't occur
The text was updated successfully, but these errors were encountered: