Skip to content

Adopt ESM #394

@AuHau

Description

@AuHau

There is a general shift in the JS ecosystem from the CommonJS module into native EcmaScript Modules. Currently, it is natively supported in the whole ecosystem, but for Node 12 it is hidden behind an experimental flag that the user would have to use.

Few of our dependencies already made the switch and that brings us to the fact that we will have to adopt it sooner or later. The main problem is that it is not possible to synchronously import ESM package, so it requires us to become ESM package in order to import those.

This switch will impose the requirement to use ESM on our users as well, so for now we are not doing the switch but in close future, it should happen. Currently, as we agreed the end-of-life of Node 12 seems like a good milestone when to revisit this as then it will be natively supported in the ecosystem without any need for flags and other barriers.

Metadata

Metadata

Assignees

No one assigned

    Labels

    P2Medium: Good to have, but can wait until someone steps updif:hardHaving worked on the specific codebase is importantkind:architectureCore architecture of projectstatus:blockedUnable to be worked further until needs are met (see 'need:*' category)type:issue

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions