Monaco-editor: Create ES6-Compliant Distribution

[fedoranimus]

While AMD is useful, it can be a pain to use in modern web applications, especially those using Typescript.

It would be excellent for this project to support an ES6 Distribution so that the following syntax (or similar) can be used:
import * as monaco from 'monaco-editor'

This would greatly ease the difficulty of implementing this tool moving forward and also help it stay standards-compliant.

Edit: Grammar

[marxo]

This would be preferable to existing solutions. We're using Meteor and using AMD modules results in conflict with other modules sometimes. Can @alexandrudima or someone else from the team explain why this would be difficult to integrate as labeled?

[alexdima]

Sorry, I struggled with the label name.

I tried to classify issues that concern how easy/difficult it is for the editor to be consumed/integrated.

[PascalPrecht]

Can we expect an update on this soon? Unfortunately, I'm not very familiar with module loading approaches, so I won't be a great help here when it comes to contributions... however, since this issue is a couple of months old, I'm wondering if there's any progress here.

Otherwise I'll see if there are other alternatives. But I think too that for Monaco's adoption, getting rid off AMD dependency is a good idea.

[DinkDonk]

This should absolutely get top priority. Would love to be able to - sanely - use monaco in a TypeScript environment.

[jarben]

Any updates on this?

[jurajhrib]

+1

[jiron12]

+1

[devmondo]

+1

[nadavwix]

+1

[vudzero]

+1

[NeekSandhu]

I think the one of the main reasons monaco is AMD based is probably because how it handles Workers. monaco internally uses require.toUrl to resolve paths to worker files. It'd huge progress towards this goal if monaco "outsources" this mechanism instead of doing it by itself.

[alexdima]

Done with #18