You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Node 19 is getting stricter about ESM modules and removing the --experimental-module-specifier flag.
Here are some big changes coming to node19 which will catch us out:
Relative imports MUST have a file extension (ie import {} from './Adaptor becomes import {} from './Adaptor.js)
Folder imports will not work ((ie import {} from './src becomes import {} from './src/index.js)
lodash-fp, which many adaptors depend on, is deprecated. Strictly speaking we should be using lodash/fp, although this isn't itself ESM compliant (see lodash/issues/5285)
The upshot of all this is that tests and maybe builds will fail when we upgrade node beyond v18.
I actually thought the experimental arguments enabled future features early. Turns out they're actually masking deprecated functionality. Whoops - that's my bad.
Note that this doesn't affect any of the built and deployed adaptors - those are ESM and CJS compliant.
The text was updated successfully, but these errors were encountered:
Node 19 is getting stricter about ESM modules and removing the
--experimental-module-specifier
flag.Here are some big changes coming to node19 which will catch us out:
import {} from './Adaptor
becomesimport {} from './Adaptor.js
)import {} from './src
becomesimport {} from './src/index.js
)lodash-fp
, which many adaptors depend on, is deprecated. Strictly speaking we should be usinglodash/fp
, although this isn't itself ESM compliant (see lodash/issues/5285)The upshot of all this is that tests and maybe builds will fail when we upgrade node beyond v18.
I actually thought the experimental arguments enabled future features early. Turns out they're actually masking deprecated functionality. Whoops - that's my bad.
Note that this doesn't affect any of the built and deployed adaptors - those are ESM and CJS compliant.
The text was updated successfully, but these errors were encountered: