Hi Mark,
Thank you for your demo!
In part one, I'm getting tripped up on the section around "Commit b55dbd5: Add scripts to build a Cesium bundle with DllPlugin."
I've been following along with every step of this demo, including grabbing the scripts from Github that you skip looking at in the demo, in re Commit b55dbd5.
When I run node ./scripts/buildCesiumDLL.js
, I don't get any asset list, and the whole process goes by in a matter of milliseconds. Which gives me the impression that something meaningful is happening when you run this build that isn't translating to when I run it.
Accordingly, there is no $PROJECT/distdll folder created, and so running node scripts/build.js
throws an error because there isn't any distdll/cesiumDLL-manifest.json file. I'm assuming the creation of this file is something that buildCesiumDLL is supposed to automate?
That said, even with deleting the cesium folder from the public directory, npm start
still runs the app. While there isn't a $PROJECT/distdll folder, there's a $PROJECT/build one that includes the cesium folder that had previously been living in public.
Any idea what's going on here? And how I can actually compress the cesium bundle (as far as I know it's still 40-some-odd kilobytes)?
Thanks,
Ben