fix: use correct export syntax in typings

[G-Rath]

This should be merged before #126.

Also to export things like the interfaces, they'll need to be wrapped in a namespace:

declare namespace Chromium {
   ...
}

---

In TS module.exports syntax is represented by export =.

The current typings will work fine if you use the default import syntax, but will fail at runtime if you use star/namespace syntax.

By using the proper export syntax, doing import * as chromium from 'chrome-aws-lambda'; will result in an error:

TS2497: This module can only be referenced with ECMAScript imports/exports by turning on the 'esModuleInterop' flag and referencing its default export.

[G-Rath]

@alixaxel any chance of getting a review on this?

[alixaxel]

@G-Rath For me, the export = Chromium; is always yielding errors:

For the first (chromiumDefault) case:

index.d.ts(20, 1): This module is declared with using 'export =', and can only be used with a default import when using the 'esModuleInterop' flag.

And for the second one (chromiumStar);

This module can only be referenced with ECMAScript imports/exports by turning on the 'esModuleInterop' flag and referencing its default export.ts(2497)

Do you experience the same?

[alixaxel]

@G-Rath I guess this is no longer needed?

[G-Rath]

Yeah, weird wonder why my IDE didn't flag it 🤔

[alixaxel]

@G-Rath Nicely done. 👍

[G-Rath]

@alixaxel yes, because it's a commonjs export, so you need esModuleInterop or to use the require import syntax:

import chromeAwsLambda = require('chrome-aws-lambda');

You can see this comment for some more info on what the import/export syntaxes compile into/from :)