[TypeScript] Unable to use a plugin with typescript

[Losses]

Just doing similar thing to demo code to add a new plugin:

And got:

Maybe there're some thong wrong with the TypeScript definition

[pimterry]

You're right, I can reproduce this, and it's incorrect, but I have no idea why it's happening. It's definitely not marked as a read-only property explicitly.

Any suggestions? Happy to take hints or PRs to get this fixed.

[pimterry]

Ok, I think I know the cause of this. The problem is that TypeScript assumes that import * as ... module export properties are always readonly. That's not true in many real environments, but I think it's required by the ES6 spec, and so will be true in native ES6 environments.

Fortunately, this is possible if you're using a default import. That was only supported in TS if you had esModuleInterop enabled, but in dcc07d1 I've now added a .default property on the root object, which makes this possible all the time.

I'll release this at 1.7.0 in a moment. To use it, just change from:

import * as log from 'loglevel';

to

import log from 'loglevel';

Both are supported in general, but to make the types happy when assigning to methodFactory in TypeScript, the latter must be used.

[ELeigh91]

Worked for me using "allowUmdGlobalAccess": true in the tsconfig.json