vitest-dev
fix: don't throw on null error, hide JSON results warning
We might corrupt JSON somehow, if user ends the process, so I think we should just skip it.
I am not sure if I understand it, why do we need to limit the stacktrace?
I left a comment explaining why. Vitest sets a limit to 100 by default, which is a lot for something we don't use internally. Building stack trace is a heavy operation in Node, as we saw in Vite for example.
Vitest sets a limit to 100 by default
Should we low it down a bit and make it configurable?
Vitest sets a limit to 100 by default
Should we low it down a bit and make it configurable?
User errors are always visible, so I don't think it's necessary. The problem is with internal usage of new Error for parsing stack trace.
User errors are always visible, so I don't think it's necessary. The problem is with internal usage of
new Errorfor parsing stack trace.
But I am not against making it configurable.