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
{{ message }}
This repository has been archived by the owner on Aug 22, 2024. It is now read-only.
The problem is that both of those will find and replace any calls to require()define() in the code at build time, and if you are using either ember-cli-stencil or the method shown in this example to load the JS, you will get errors when stencil tries to call customElements.define(). ember-esri-loader@4.00+ is designed to avoid those errors, but they will still show up in production builds. There's a workaround for that. A similar hack may work for emebr-cli-amd.
I think it would be good to at the very least document ^^^ in the README.
I suspect most apps that use this will want to also use the ArcGIS API for JavaScript. In Ember, you need either one of these addons:
ember-cli-amd
ember-esri-loader
The problem is that both of those will find and replace any calls to
require()
define()
in the code at build time, and if you are using either ember-cli-stencil or the method shown in this example to load the JS, you will get errors when stencil tries to callcustomElements.define()
. ember-esri-loader@4.00+ is designed to avoid those errors, but they will still show up in production builds. There's a workaround for that. A similar hack may work for emebr-cli-amd.I think it would be good to at the very least document ^^^ in the README.
We could take it a step further and add ember-esri-loader to this repo and try and work through the trouble I was having trying to keep
customElements
from getting mangled in production builds and see if we can come up w/ a less hackish work around.The text was updated successfully, but these errors were encountered: