You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello guys, I was reviewing this project and a single question arrived to me: Do we really need to use a new webpack configuration?
I'm probably missing some context on the migration to ESmodules, but as far as I understand the further changes are:
Point the import cesium to Cesium/Source. That's working from my side with cra.
Import the widgets.css: If you import it from anywhere in your app is going to be bundled, you just need to do import 'cesium/Build/Cesium/Widgets/widgets.css'
Copy the Cesium assets:
Instead of using webpack for copying Workers, ThirdParty, Assets, Widgets, you can just add a pre-script and copy them with a single command to your /public folder. And add that folder to your .gitignore.
I know this point is not the cleanest, but in a real project are you willing to maintain craco + craco-cesium for a single library?
I know there is an issue with the dependency warnings, but makes more sense to push Cesium to perform any improvement.
Thanks for the time doing this!
The text was updated successfully, but these errors were encountered:
Hello guys, I was reviewing this project and a single question arrived to me: Do we really need to use a new webpack configuration?
I'm probably missing some context on the migration to ESmodules, but as far as I understand the further changes are:
cesium
toCesium/Source
. That's working from my side with cra.widgets.css
: If you import it from anywhere in your app is going to be bundled, you just need to do import'cesium/Build/Cesium/Widgets/widgets.css'
Instead of using webpack for copying
Workers
,ThirdParty
,Assets
,Widgets
, you can just add a pre-script and copy them with a single command to your/public
folder. And add that folder to your .gitignore.I know this point is not the cleanest, but in a real project are you willing to maintain craco + craco-cesium for a single library?
Thanks for the time doing this!
The text was updated successfully, but these errors were encountered: