convert from CJS to ESM

[dynst]

Electron 28 and newer has ESM support now.

[Naq302]

When "type": "module", is added exports": "build/main/electron.js" shows a `String does not match the pattern of "^./". warning.

yarn dev fails
error during start dev server and electron app:
Error: No entry point found for electron app, please add a "main" field to package.json

Could be fixed via

"main": "./build/main/electron.js",
  "exports": {
    ".": "./build/main/electron.js"
  },

[Naq302]

@dynst getting an error when doing a rebuild:

start electron app...

App threw an error during load
Error [ERR_MODULE_NOT_FOUND]: Cannot find module '/asgardex-desktop/node_modules/fp-ts/lib/Either' imported from /asgardex-desktop/build/main/electron.js
Did you mean to import "fp-ts/lib/Either.js"?
A JavaScript error occurred in the main process
Uncaught Exception:

Not sure why as Either is imported and present. I assume they need to be imported differently in electron.ts but not sure.

[dynst]

ESM import distinguishes between importing /Either and /Either.js, the filename extension is the difference there. But there shouldn't be a difference, if Vite is specifically configured to search for .ts and .js files if an extension is omitted:

asgardex-desktop/electron.vite.config.mjs

Line 23 in aae5c1b

extensions: ['.ts', '.js']

https://vite.dev/config/shared-options#resolve-extensions

But that field has a decent default, anyway, even if it wasn't set. And it's only applicable to internal files, not for external dependencies.

I guess we're not supposed to reach into the /lib/ internal directory structure of a dependency. Instead we should:

import { either as E } from 'fp-ts'

There's a lot of import statements just like this one that bypass the module's official top-level export API, and they'll all need rewriting.