New build style in 1.24 and 1.25 causing new errors

[cranberyxl]

New build style in 1.24 and 1.25 causing new errors

[ruicsh]

hi, 1.26 reverts back to having CommonJS as the default format, so everything should work as before.

btw, I'm cutting a new version (v2) where ESM will be the default format, and CommonJS a deep import

[ruicsh]

actually if you're using node >= 13.10.0, you can use v2.4.0 and keep the code as is:

const dynoexpr = require('@tuplo/dynoexpr');

more details here: https://github.com/tuplo/dynoexpr#install

[cranberyxl]

While this approach now works for command-line node, it doesn't work for jest. What are the advantages of making this breaking change?

[ruicsh]

you can still use v1.26.0, it works as before.

Having ESM export as default is where the ecosystem is going, other library makers have made that jump (ex: sindresorhus).

[ruicsh]

for v1, it stays the same.

for v2, while Jest doesn't support ESM natively, you'll need to import the CJS version explicitly

const dynoexpr = require('@tuplo/dynoexpr/cjs');

I've added a Jest/CommonJS e2e test here https://github.com/tuplo/dynoexpr/blob/main/e2e/main-cjs.test.js

[cranberyxl]

I would have to change every place I import dynoexpr to use the deep import so jest works. I don't understand the value.

[ruicsh]

I understand your frustration, but v1.x has no changes and will keep being supported until all kinks with ESM are fixed.

[ruicsh]

@cranberyxl you can use a configuration on Jest to keep using require('@tuplo/dynoexpr') with v2.x (while Jest doesn't support ESM)

 {
   "jest": {
     "moduleNameMapper": {
       "dynoexpr$": "<rootDir>node_modules/@tuplo/dynoexpr/cjs"
    }
  }
}