ArcGIS JSAPI Build Tips

• arcgis-webpack-plugin

  1 133 0.0 JavaScript

  Discontinued Webpack plugin for the ArcGIS API for JavaScript

  

Up until this recent release, you would only want to use the @arcgis/webpack-plugin if you want to copy the assets locally. This would add about 25mb to your deployed build size. This includes the workers, styles, images, and localization files. If you did not want to copy them locally and just let them load from the CDN, you didn't need this plugin with webpack at all.

• jsapi-resources

  3 688 7.5 JavaScript

  A collection of useful resources for developers using the ArcGIS API for JavaScript.

  

Using these build tips and tweaks, the sample application shown here is about 710kb of JavaScript at runtime, and it has some widgets and custom visualizations in it. I'm pretty happy with that.

• SurveyJS

  surveyjs.io featured

  Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App. With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js.

  

• arcgis-js-build-experiments

  1 0 0.0 JavaScript

I put a repo together here of these two build scenarios if you want to try it out yourself. At the end of the day, if you really need to squeeze out every last kb from your deployed and runtime size, you can use webpack to get there. If you want simplicity, I think ViteJS is a great choice. It all depends on your circumstances. You can also watch me walk though this in the video below.

• vite

  791 64,913 9.9 TypeScript

  Next generation frontend tooling. It's fast!

  

But what if I use something simple like ViteJS? I'm a big fan of ViteJS, and like it quite a bit. The benefit here is you can run it without a single config file. Here are the stats of using ViteJS versus webpack for a custom build. Runtime numbers are compressed.

Suggest a related project