Optionally preserve current stack · sindresorhus/serialize-error#98

(6 评论) (0 反应) (0 负责人)JavaScript (599 star) (69 fork)user submission

enhancementhelp wanted

描述

An issue I found when throwing deserialized errors is that the thrown error has no reference to this throw point.

I think the "correct" way to throw serialized errors would be something like:

throw new Error(serialized.message, {
	cause: deserializeError(serialized),
});

Two drawbacks:

new Error doesn't benefit from https://github.com/sindresorhus/serialize-error/pull/70
this isn't necessarily what people want or expect by default

So how about:

throw deserializeError(serialized, {preserveStack: true});

技术栈: javascript
领域: backend
议题类型: feature
难度: 2
预计时间: 1-3 hours
活动状态: fresh
清晰度: clear
前置要求: 无
新手友好度: 65
研究方向: The issue proposes adding a `preserveStack` option to the `deserializeError` function. The implementation would involve modifying the function in the main source file (likely `index.js`) to accept an options object with `preserveStack` boolean. When true, the current stack should be preserved using the `cause` property or a different approach. The discussion references PR #70 which attempted similar functionality. Maintainers have not yet responded with specific guidance on the preferred implementation.