An Ember addon that wraps the esri-loader library to allow lazy loading and preloading the ArcGIS API for JavaScript in Ember applications.
See the esri-loader README for more information on why this is needed.
- Ember.js v3.20 or above
- Ember CLI v3.20 or above
- Node.js v12 or above
In your app's root folder run:
npm install esri-loader
ember install ember-esri-loaderHere's an example of how you could load and use the latest 4.x MapView and WebMap classes in a component to create a map:
// app/components/esri-map.js
export default Ember.Component.extend({
layout,
esriLoader: Ember.inject.service('esri-loader'),
// once we have a DOM node to attach the map to...
didInsertElement () {
this._super(...arguments);
// load the map modules
this.get('esriLoader').loadModules(['esri/views/MapView', 'esri/WebMap']).then(modules => {
if (this.get('isDestroyed') || this.get('isDestroying')) {
return;
}
const [MapView, WebMap] = modules;
// load the webmap from a portal item
const webmap = new WebMap({
portalItem: { // autocasts as new PortalItem()
id: this.itemId
}
});
// Set the WebMap instance to the map property in a MapView.
this._view = new MapView({
map: webmap,
container: this.elementId
});
});
},
// destroy the map view before this component is removed from the DOM
willDestroyElement () {
if (this._view) {
this._view.container = null;
delete this._view;
}
}
});See the esri-loader documentation on loading modules for more details.
Before you can use the ArcGIS API in your app, you'll need to load the styles. See the esri-loader documentation on loading styles for more details.
The above code will lazy load the ArcGIS API for JavaScript the first time loadModules() is called. This means users of your application won't need to wait for the ArcGIS API to download until it is need.
Alternatively, if you have good reason to believe that the user is going to transition to a map route, you may want to start pre-loading the ArcGIS API as soon as possible w/o blocking template rendering. You can add the following to the application route:
import { inject as service } from '@ember/service';
import Route from '@ember/routing/route';
export default class ApplicationRoute extends Route {
@service esriLoader
beforeModel() {
// Preload the JS & CSS for the latest (4.x) version of the JSAPI
this.esriLoader.loadScript({ css: true })
.catch(err => {
// TODO: better way of showing error
window.alert(err.message || err);
});
}
}Now you can use loadModules() in components to create maps or 3D scenes. Also, if you need to, you can use isLoaded() anywhere in your application to find out whether or not the ArcGIS API has finished loading.
This addon also includes a mixin that can be help mitigate one of the primary pain points of using esri-loader: accessing modules is always asynchronous. That's fine for modules like esri/map where you expect to be using them in an asynchronous operation (like creating a map). However, it can be cumbersome when you just need something like a new Graphic() to add to that map.
Services or components that implement the esri-module-cache mixin can load all the modules they may need up front during an async operation (such as creating a map), and then use the mixin's cacheModules() function to store references to any of those modules so they don't have to be loaded again. Later the getCachedModule() and newClassInstance() functions can be used to synchronously access and use the modules that have already been loaded. For example:
// map-service.js
import Service, { inject as service } from '@ember/service';
import EsriModuleCacheMixin from 'ember-esri-loader/mixins/esri-module-cache';
export default Service.extend(EsriModuleCacheMixin, {
esriLoader: service('esri-loader'),
loadMap (elemendId, options) {
return thigs.get('esriLoader').loadModules([
'esri/map',
'esri/Graphic'
]).then(([Map, Graphic]) => {
// cache graphic module later for synchronous use
this.cacheModules({ Graphic });
// create and return the map instance
return new Map(elementId, options);
});
},
// NOTE: this will throw an error if it is called before loadMap()
newGraphic (...args) {
return this.newClassInstance('Graphic', ...args);
}
});// my-map/component.js
export default Component.extend({
layout,
mapService: service(),
// once we have a DOM node to attach the map to...
didInsertElement () {
this._super(...arguments);
// load the map
this.get('mapService').loadMap(this.elementId, { basemap: 'gray' })
.then(map => {
this.map = map;
})
},
actions: {
addGraphic (x, y) {
if (!this.map) {
// can't call newGraphic() unles map has loaded
// also no point in creating a gaphic if there's no map to add it to
return;
}
const graphicJson = {
geometry: {
x,
y,
spatialReference: {
wkid: 4326
}
},
symbol: {
color: [255, 0, 0, 128],
size: 12,
angle: 0,
xoffset: 0,
yoffset: 0,
type: 'esriSMS',
style: 'esriSMSSquare',
outline: {
color: [0, 0, 0, 255],
width: 1,
type: 'esriSLS',
style: 'esriSLSSolid'
}
}
};
const graphic =
this.get('mapService').newGraphic(graphicJson);
this.map.graphics.add(graphic);
}
}- additionalFiles: list of strings or RegExp objects, defaults to []. Identifies additional files in which we should replace
requireanddefine. This can be particularly helpful if also using ember-auto-import 2.x, which places its modules in separate js files and attempts to capture therequireanddefinethe app is using. The configuration example above shows how to support ember-auto-import 2.x with the default webpack configuration, but you can add additional globs as necessary.
If you are using ember-auto-import you will have to configure ember-auto-import to exclude any imports from esri-loader. Furthermore, if you are using ember-auto-import v2.x you will need to configure ember-esri-loader to process the ember-auto-import output using additionalFiles. To do so, add the following options in your ember-cli-build.js file:
// ember-cli-build.js
let app = new EmberApp(defaults, {
autoImport: {
// ember-esri-loader loads esri-loader with a script tag to prevent it from being rewritten to replace "require"
// and "define" in the build pipeline. We need to exclude it from ember-auto-import so that we don't pull it
// back into the build pipeline when we import it ourselves.
exclude: [ 'esri-loader' ],
}
'ember-esri-loader': {
// this is only needed for ember-auto-import 2.x
additionalFiles: [ /chunk\.app\..*\.js/ ],
}
}
This addon is an implementation of the "Dedicated Loader Module" pattern for Ember. It is a mashup of the ideas from angular2-esri-loader and ember-cli-amd. Like angular2-esri-loader, it creates a service that exposes functions that wrap calls to the esri-loader library to load the ArcGIS API and it's modules in promises. However, in order to avoid global namespace collisions with loader.js's require() and define() this addon also has to steal borrow from ember-cli-amd the code that finds and replaces those terms with their pig-latin counterparts in the build output. However unlike ember-cli-amd, it does not inject the ArcGIS for JavaScript in the page, nor does it use the ArcGIS API's Dojo loader to load the entire app.
You cannot use ES2015 module syntax for ArcGIS API modules (i.e. import Map from 'esri/map';) with this addon. If you do not feel that your application would benefit from lazy-loading
the ArcGIS API, and you'd prefer the cleaner abstraction of being able to use
import statements, you can use ember-cli-amd.
Using this addon to load ArcGIS API for JavaScript v4.x modules in tests run in PhantomJS may cause global errors. Those errors did not happen when running the same tests in Chrome or FireFox.
Also, this addon cannot be used in an Ember twiddle.
In addition to ArcGIS Online applications such as ArcGIS Hub, the following open source applications use this addon:
MyStreet - A municipality viewer that allows users to input an address and receive information based on that location uses this addon to lazy load v3.x of the ArcGIS API only when an app uses a map.
The dummy application for this addon demonstrates how to pre-load v4.x of the ArcGIS API.
- fork and clone the repository
cd ember-esri-loadernpm install
npm run lint:hbsnpm run lint:jsnpm run lint:js -- --fix
ember test– Runs the test suite on the current Ember versionember test --server– Runs the test suite in "watch mode"ember try:each– Runs the test suite against multiple Ember versions
ember serve- Visit the dummy application at http://localhost:4200.
Find a bug or want to request a new feature? Please let us know by submitting an issue.
Esri welcomes contributions from anyone and everyone. Please see our guidelines for contributing.
Copyright 2017 Esri
Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.
A copy of the license is available in the repository's license.txt file.