Feature/es module commonjs

[ols]

ES module and CommonJS

Current approach is the following: Exporting dist with esm and commonjs for non-react jsx, which is logary, logary-plugin-browser, logary-plugin-node. logary-plugin-nextjs and logary-plugin-react is only using commonjs.

This means that when we run with-nextjs and with-nextjs-app we are using commonjs but when we are bundling logary-browser we are using esm with tree-shaking to get minimal bundle min file.

Here is some findings regarding es2015 usage as module rather than CommonJS

When using es2015 as module type in tsconfig.js you will get the following error:
SyntaxError: Cannot use import statement outside a module:

• Support ES module format (ESM) in next.config.js vercel/next.js#9607
  • “When using type: module in package.json on Node v13.1.0 and an ESM next.config.js format, Next throws an error due to the config resolution logic relying on require.”
• https://fredriccliver.medium.com/syntaxerror-cannot-use-import-statement-outside-a-module-69182014b8c6
• SyntaxError: Cannot use import statement outside a module vercel/next.js#15957
• SyntaxError: Cannot use import statement outside a module TypeStrong/ts-node#922
  • “You’re trying to execute use it as an ES2015 module, but node.js currently understands CommonJS.”

The recommended approach here is to use “type”: “module” defined in package.json.

But when setting type as module it will result in the following error:
Error [ERR_REQUIRE_ESM]: Must use import to load ES Module:

Here is a possible solution which does not work:

• ERR_REQUIRE_ESM when requiring .eslintrc.js eslint/eslint#12319 (comment)

Another possible approach is to use both ES Module and CommonJS which is allowing the consumer to choose.

• https://blog.logrocket.com/publishing-node-modules-typescript-es-modules/
  • “Node doesn’t yet support ES modules out of the box. It’d be great to publish a CommonJS version, too, so Node works with no extra effort. ES module support is coming in Node 13 and beyond, but it’ll be a while before the ecosystem catches up.”

Some more readings in the subject:

“they are already interpreted with a conflicting opinion. TS produces a JS file that the JS code it produces does not point to. ES6 is the closest thing to an officially correct way to do JavaScript, so if the ES6 code produced by TypesScript is wrong, this is a bug plain and simple. There is no need to wait for any proprosals and such, just fix TypeScript's bug. But today people feel that if they don't find fault with something and put it through 10 layers of proposal before acting, then they are not acting intellectually. Give me a break.”

• Provide a way to add the '.js' file extension to the end of module specifiers microsoft/TypeScript#16577

[haf]

+1 but squash when you merge.

[haf]

How is it we don't use window which is customary?