arcgis-js-api npm package size

Question

When I install the dependencies of the arcgis-js-api npm package, it installs 133MB of node_modules. When inspecting the contents of node_modules I discovered that there is a 15MB zip file in dojo-util/buildscripts (the entire buildscripts folder is over 20MB). There are are also 13MB of .jar files which seem to be useful for build time and 12MB of .html files and 11MB of .jpg files that are used almost exclusively for tests of the dojo*/dijit packages.

When looking at the package.json file for arcgis-js-api, none of the dependencies are devDependencies. To reduce bundle size for applications that depend on arcgis-js-api, is it possible to move any dependencies to devDependencies? Furthermore, for packages that cannot be moved, is it possible to remove the tests and other non-runtime code from ESRI's forks of the dojo*/dijit packages that the arcgis-js-api depends on?

MichaelHeavenor · Answer

Thank you for your quick reply! Thanks for that list.

ReneRubalcava · Answer

For 4.15, this is what is needed and will be the deps. "dependencies": { "@dojo/framework": "5.0.4", "dojo": "Esri/dojo#v1.14.2/esri-3.28.0", "dojo-dstore": "1.1.2", "dojox": "Esri/dojox#v1.14.2/esri-3.28.0", "maquette-css-transitions": "~1.1.1", "maquette-jsx": "~2.1.1", "moment": "2.24.0" },‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ This will change at 4.16.

MichaelHeavenor · Answer

Hello Rene,

I had heard about the move off of dojo and I am glad to hear the some dependencies are being removed for 4.15. Splitting off dojo-util is a good idea 🙂

My project just uses the plain arcgis-js-api package without the need to use dojo to generate a custom build of the package. In this case, I only need runtime dojo dependencies. Which of the dojo dependencies are only needed for runtime? It seems like if I would like to trim the dojo packages by removing the tests (and other unneccesary files for runtime) I will have to fork the Esri/dojo packages and possibly arcgis-js-api itself.