Does not work if defaultJSExtensions: true is used

[DaveEmmerson]

In our project, we set defaultJSExtensions: true in our config.js, this is to fit in with the template we're using.

This doesn't play well with esri-system-js. When getName is called, the location it is passed isn't, e.g., esri/Color, it's esri/Color.js.

The result is that in _register, the name doesn't match the supplied list of module names and the modules aren't registered with SystemJS.

I've fixed the issue in a fork that we're going to use, but I was wondering if the change might be included in the library itself? I can submit a pull request if it's seen to be a good thing.

Thanks

Dave

[DaveEmmerson]

It might be that a config.js change can fix this. Thinking a package for esri that does defaultExtension: false.

Will update if I figure it out.

[DaveEmmerson]

The answer was:

"esri": {
  "defaultExtension": false
}

In the config.js

Ah well, I've learned a lot about our setup and about esri-system-js in the process :)