Worms David

@realtebo I you can make the change, try updating your "module" definition to "ESNext" or "NodeNext". Not a specialist in that field but it could help.

No, there hasn't been any feedback for now.

Would it be possible to simply expose a hook where we could implement our own coercion rule, I have many situation where implementing my own coersion or no coersion at...

Could you share the code generating this error. We changed the build and it will help to know how the error is generated.

It was meant to be a major version but instead of `npm run release:major`, I executed `npm run release major` only to find too late about my mistake. `npm unpublished`...

Two new versions are published: - version 1.8.1 fixes 1.8.0 and is a copy of the previous version 1.7.4 - version 2.0.0 is the new version with the convertions to...

Closing, please open a new issue if you encounter problems with version 2.

Hi mgnmpk, The package has been maintained lately, lack of time on our side, so no support around it for now.

It seems like you are using TypeScript. The repo [http-status-import-bug](https://github.com/dschuessler/http-status-import-bug) provided above is configured for CommonJS. - no "type" field set to "module" in the package.json file, add ```json {...

Please share your envionnement (Browser/Node.js, CommonJS/ESM, JS/TS, ...). For example, there shouldn't be a need to import `/dist` with Node.js.