Allow for lazy loading of monaco

[gatesn]

It's fine to import X = monaco.X for types, but not for objects such as monaco.Uri and monaco.languages. This PR inlines these references to allow monaco to be loaded lazily.

Fixes #16

[akosyakov]

@gatesn please sign off your commit, git commit --amend -s

Does this PR solve an issue with react-monaco-editor integration? Would you be able to add react-example in the root?

[gatesn]

Signed commit, will check out the react issue as well

[gatesn]

Not sure it's worth writing an example here given the amount of duplicated code between the react and non-react examples. Also #16 is already closed.

[akosyakov]

Would it be possible to add a react page to the existing example?

[gatesn]

@akosyakov working on the example, I try to compile it and get this, have you seen it before? Is it an update in the jsonrpc package?

src/client/client.ts(43,18): error TS2554: Expected 1 arguments, but got 0.
src/client/client.ts(60,57): error TS2345: Argument of type 'MessageConnection' is not assignable to parameter of type 'MessageConnection'.
  Types of property 'sendRequest' are incompatible.
    Type '{ <R, E, RO>(type: RequestType0<R, E, RO>, token?: CancellationToken | undefined): Thenable<R>; <...' is not assignable to type '{ <R, E, RO>(type: RequestType0<R, E, RO>, token?: CancellationToken | undefined): Thenable<R>; <...'. Two different types with this name exist, but they are unrelated.
      Types of parameters 'type' and 'type' are incompatible.
        Type 'RequestType0<any, any, any>' is not assignable to type 'RequestType0<any, any, any>'. Two different types with this name exist, but they are unrelated.
          Types have separate declarations of a private property '_'.

[jkillian]

Nice fix! Can this be merged and the react-example added as a separate PR? They don't feel extremely related to me.

[akosyakov]

@gatesn please use git rebase origin/master instead of merge to catch up with changes in the master

[akosyakov]

@jkillian if you don't use react-monaco-editor, what does it fix for you?

[jkillian]

@akosyakov we use monaco's loader.js script to load monaco. If this library gets imported before monaco is loaded (which is very likely since for the most part we use static imports at the top of our files and then bundle with webpack), it'll throw an error since monaco isn't yet defined as a value.

[akosyakov]

@gatesn yes, with npm5 the example is broken because of symlinks used for file: and tsc was not able to preserve them leading to resolving MessageConnection from 2 different places

I've opened a PR to fix it #25, please review it.

[akosyakov]

Please have a look at comments

[akosyakov]

@gatesn please assign you on #4 (comment) if you are going to tackle the react example. I am fine to make it with the separate PR but please take care of the proper rebasing.

[akosyakov]

@gatesn I've sent an invite you that makes you a collaborator. You should be able to merge after accepting it.