ono
ono copied to clipboard
JS-DevTools
Wrap errors without losing the original message, stack trace, or properties
**Description** I've detected problematic usage of source maps from [@jsdevtools/[email protected]](https://www.npmjs.com/package/@jsdevtools/ono/v/7.1.3). Issue is manifesting when using for example [Create React App](https://www.npmjs.com/package/create-react-app/v/5.0.0) to build the application using `@jsdevtools/[email protected]` as an npm package....
Importing inspect form utils isn't supported in vite. This project is imported by some other projects and it breaks the build. Is it possible to remove the import?
Hiya, thank you for this great library! I was wondering if this is possible to do today or if it could be implemented as an enhancement? Right now the stack...
I see that the `toJSON` is deliberately used for the `Symbol.for('nodejs.util.inspect.custom')` custom formatter. This doesn't feel very conducive to clear and concise error messages. Take the following for example and...
This PR fixes a tiny bug where `module.exports` exists but `module.exports.default` does not. An additional check is added to the conditional before proceeding.
https://github.com/JS-DevTools/ono/blob/a1fa89a25e7432f7615af8b4179f842b5affccf2/src/index.ts#L10-L13 This code block is bombing my rollup build. Not caught during build. This code makes it into the bundle, and then it fails on runtime startup. `module.exports.default` is undefined...
Metadata
Owner
Metadata
Wrap errors without losing the original message, stack trace, or properties