Load Mustache with require in each module that uses it

[TomMalbran]

Instead of having Mustache being loaded in the index and being a global variable, it can be loaded using require creating a module for it in each module that needs to use Mustache, as every other module in brackets is loaded.

[njx]

Reviewed. This might make sense, but we don't want to do it right now because it might break existing extensions. We're planning to overhaul the extensibility API soon, and should discuss this as part of that. So let's not submit any pull requests for this yet :)

/cc @dangoor

[TomMalbran]

@njx Since we changed how we load CodeMirror, should we change this in the current Sprint too, so that extension developers could fix both requires at the same time?

But fixing this might be harder depending on how we do the require.

[redmunds]

This issue is unassigned, so marking "Needs Review".

[dangoor]

@TomMalbran We didn't get back to reviewing this in time for release 38. Would you be interested in doing this in release 39?

We'd want to do it like CodeMirror where the global is still available but has a DeprecationWarning.

[TomMalbran]

Sure, I will. That is a good solution to not break anything.

[ficristo]

Done with a deprecation warning in: #11616