Up until now, the module has ESM import/export syntax but it's not marked as an ESM module. That means that only bundlers can import/use it directly, and "regular" Node.js or non-mixed bundlers cannot.
This PR makes the package into a real ESM package that follows the ESM import/export conventions.
We also get import paths without dist in them
There's also an ESLint package and rule to make sure we continue following ESM guidelines for package extensions and don't make many mistakes
Up until now, the module has ESM import/export syntax but it's not marked as an ESM module. That means that only bundlers can import/use it directly, and "regular" Node.js or non-mixed bundlers cannot.
This PR makes the package into a real ESM package that follows the ESM import/export conventions.
We also get import paths without
dist
in themThere's also an ESLint package and rule to make sure we continue following ESM guidelines for package extensions and don't make many mistakes