ember-cli / loader.js

minimal amd loader mostly stolen from wycats.
MIT License
79 stars 69 forks source link

support noConflict mode #139

Open stefanhofmann2 opened 5 years ago

stefanhofmann2 commented 5 years ago

I want to integrate an external amd packages which uses requirejs. The problem is that the Ember loader is conflicting with the AMD loader. How can i use the 'No conflict' mode with the Ember loader?

ggayowsky commented 5 years ago

I am having a similar problem, wanting to use no conflict because ArcGIS JS uses dojo require under as the global require which is not compatible with loader.

While the noConflict mode would be great to use nobody in slack/discord has any idea of how/if it would work and (it seems like nobody who maintains this repo knows either). If that is the case why even mention it in the documentation?

I would be willing to document this if I can get it successfully working, but would need help.

rwjblue commented 5 years ago

No conflict mode in the loader itself does work fine, the issue (when talking about a normal ember-cli app) is that many other parts of the system assume global require and define (we could come up with a checklist). I totally think it would be a great thing to make a nice abstraction to allow ember-cli apps work well with no conflict mode. It largely just needs some TLC...

ffaubry commented 5 years ago

@ggayowsky Did you looked at either:

ggayowsky commented 5 years ago

@ffaubry I am using those addons and trying to find a way around them because I dont like the solution. (doesnt work with ember-auto-import, cannot self host arcgis files on version >0.4.9, cannot use decorators or other experimental features because of the esprima dependency, breaks source maps and thus cannot debug using VS code).

If I ever find out how to use babel to do the transformation and only have it affect the ember app files I will contribute to those repositories.

ffaubry commented 5 years ago

@ggayowsky See comments under https://github.com/Esri/ember-cli-amd/issues/39 Let's move the conversation under that repo.