Add ESM support

[near]

Add ESM support

[itegulov]

@cristobal if you do start working on this issue feel free to take a look at my attempt I made a couple of weeks ago: bf616b5. As you said, I had to get rid of bs58, but base-x itself did not have ESM support either so I tried to temporarily copy its content in place. The end result seemed to work fine with vite, so I am not sure if we actually need to do anything about bn.js and text-encoding-utf-8, but I could very well be wrong.

[cristobal]

Ok will start working on this next week, if i manage to get some time free this weekend i will look into it but otherwise expect some PR's from next week 🙂 👍🏽

[volovyks]

Thanks, @cristobal ! Let's move step by step.
We can merge breaking changes to a separate branch and then release them together with a new major version update.

[cristobal]

Let's add ESM alongside CJS to this project. Can be a requirement for near/near-api-js#607 cc @itegulov

Why not remove dependency on text-encoding-utf-8 and make it an optional polyfill, since the module actually does not export an default which is the one used here

// TODO: Make sure this polyfill not included when not required
import * as encoding from "text-encoding-utf-8";

Leaving this part out or modifying the text-encoding-utf-8 to include a default export, works when building with Esbuild or Snowpack i commented this in #47.

[cristobal]

Perhaps some contribution to both the bn.js and bs58 to have proper esm build and exports?

Not sure if bs58 should be an dependency, due to the few lines of code:

const basex = require('base-x')
const ALPHABET = '123456789ABCDEFGHJKLMNPQRSTUVWXYZabcdefghijkmnopqrstuvwxyz'

module.exports = basex(ALPHABET)

perhaps rather just depend on base-x instead?

[volovyks]

@cristobal looks reasonable! Do you think you can create a PR?

[cristobal]

@cristobal looks reasonable! Do you think you can create a PR?

Sure could try do make some PR's, what do you prefer one big PR or several smaller changes?

• Replacing bs58 by using base-x directly would not be that hard and could be a minor upgrade.
• Removing text-encoding-utf-8 and specifying it as a polyfill where needed is a major upgrade since it would require those that need to support older browsers have to manually polyfill it.
• I think bn.js may be a bit trickier related issue on ethers.js with esm build.

@volovyk-s Thoughts on the process?

[volovyks]

@cristobal I have created develop-breaking branch for breaking changes. You can target it in your PR's.

[ailisp]

Supported in 1.0!