Select to view content in your preferred language

Please include map-components in the JS API zip download

300
3
a month ago
Status: Under Consideration
Labels (2)
GILBERTNG1
Occasional Contributor

I noticed that there is no equivalent of https://js.arcgis.com/4.33/map-components/ included in this subfolder in the latest ArcGIS JS API 4.33 download: 

arcgis_js_v433_api.zip\arcgis_js_v433_api\arcgis_js_api\javascript\4.33\@arcgis

Our GIS organization hosts the JS API internally on a separate IIS virtual directory, rather than installing the API on every GIS web app Visual Studio solution. Please include the new compiled JS map components (widget replacements) in the zip file download. 

3 Comments
Noah-Sager

Hi @GILBERTNG1, thank you for posting your idea here. We are going to review our download story and improve it to explain how to get the components locally. It won't be zipped and included with the API, but you can download directly from npm registry url.

More information is available in this guide topic: https://developers.arcgis.com/javascript/latest/working-with-assets/ 

For components, the CDN files are available thru npm in the "dist/cdn" folder. You can get them with npm or direct http. For example:

npm install @arcgis/map-components

or

curl https://registry.npmjs.org/@arcgis/map-components/-/map-components-4.33.16.tgz

Noah-Sager
Status changed to: Under Consideration
 
VenkataKondepati
Good observation, I’ve run into the same challenge when hosting the JS API internally. Having the map components included directly in the downloadable API package would make it much easier to keep internal deployments consistent without extra workarounds. Right now, the missing pieces create unnecessary friction for organizations that manage the API on-premises rather than pointing to the CDN. Including the compiled map components in the official zip would align the download with what’s available online and support a lot of enterprise customers that rely on internal hosting for stability, security, or offline environments. +1 to this request, it would simplify internal distribution and reduce overhead for admins. Regards, Venkat