See release notes -- all you have to do is change this line to
-- import hexoid from 'hexoid';
++ import { hexoid } from 'hexoid';I couldn't get the base branch to pass lint or tests, otherwise I would have sent PR.
This release solves issues like:
Sorry about the noise / trouble, but as I'm sure you all are aware & familiar with, the ESM rollout was problematic and (un)fortunately not specific to hexoid.
Aside from the named export change, hexoid added an exports map. Given that your CI here only runs on Node 18+, you may not care, but there are some obscure Node versions (13.0 - 13.7, iirc) that don't work with "exports" maps. However, these users should (1) not be using those versions to start with, they're experimental & super broken (2) these users are 99% likely using webpack or something anyway, which likely bundles everything up and skips Node requires anyway.
See release notes -- all you have to do is change this line to
I couldn't get the base branch to pass lint or tests, otherwise I would have sent PR.
This release solves issues like:
hexoidin formidable@2.0.1 #871Sorry about the noise / trouble, but as I'm sure you all are aware & familiar with, the ESM rollout was problematic and (un)fortunately not specific to hexoid.
Aside from the named export change, hexoid added an exports map. Given that your CI here only runs on Node 18+, you may not care, but there are some obscure Node versions (13.0 - 13.7, iirc) that don't work with
"exports"maps. However, these users should (1) not be using those versions to start with, they're experimental & super broken (2) these users are 99% likely using webpack or something anyway, which likely bundles everything up and skips Noderequires anyway.