sindresorhus/serialize-error

`cause` prop is not being serialized

Closed this issue · 4 comments

razbensimon commented

See those 2 examples:
image

any reason why? or how should it be supported?
Thanks

sindresorhus commented

We have a test that proves it's working:

serialize-error/test.js

Lines 151 to 168 in d9074a6

test('should serialize the cause property', t => {
const error = new Error('outer error');
setErrorCause(error, new Error('inner error'));
setErrorCause(error.cause, new Error('deeper error'));
const serialized = serializeError(error);
t.is(serialized.message, 'outer error');
t.like(serialized.cause, {
name: 'Error',
message: 'inner error',
cause: {
name: 'Error',
message: 'deeper error',
},
});
t.false(serialized.cause instanceof Error);
t.false(serialized.cause.cause instanceof Error);
});

Make sure you are on the latest version.

razbensimon commented

@sindresorhus I used version 8, sorry for that.
I tried to upgrade it to v11 but now having an issue in my jest tests suite:

 Test suite failed to run

    Jest encountered an unexpected token

    Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax.

    Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration.

    By default "node_modules" folder is ignored by transformers.

    Here's what you can do:
     • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it.
     • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript
     • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config.
     • If you need a custom transformation specify a "transform" option in your config.
     • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option.

    You'll find more details and examples of these config options in the docs:
    https://jestjs.io/docs/configuration
    For information about custom transformations, see:
    https://jestjs.io/docs/code-transformation

    Details:

    /Users/my-user/node_modules/.pnpm/serialize-error@11.0.2/node_modules/serialize-error/index.js:1
    ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){import errorConstructors from './error-constructors.js';
                                                                                      ^^^^^^

    SyntaxError: Cannot use import statement outside a module

Is there a workaround? Does the library build have a problem with jest by default?

talatkuyuk commented

@razbensimon I am facing the same error "SyntaxError: Cannot use import statement outside a module" with jest.

How did you solve the issue?