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
It would be nice if esri/arcgis/utils was not required unless it was needed (i.e. unless application calls createWebMap()). I've found for a simple application that uses createMap() and then adds a single feature layer, I can shave off ~30kb of JavaScript by commenting out the code that requires esri/arcgis/utils.
This could be done w/o changing the API by using a nested require block inside createWebMap(). I'm not aware of any drawbacks to that.
Just wanted to get other people's thoughts on this idea.
The text was updated successfully, but these errors were encountered:
It would be nice if
esri/arcgis/utils
was not required unless it was needed (i.e. unless application callscreateWebMap()
). I've found for a simple application that usescreateMap()
and then adds a single feature layer, I can shave off ~30kb of JavaScript by commenting out the code that requiresesri/arcgis/utils
.This could be done w/o changing the API by using a nested require block inside
createWebMap()
. I'm not aware of any drawbacks to that.Just wanted to get other people's thoughts on this idea.
The text was updated successfully, but these errors were encountered: