Skip to content

test: fix edge snapshot stack traces

Working on https://github.com/nodejs/node/pull/49657, I discovered that some of the more unusual snapshot tests had stack traces that include specifics of the module loader internals. (See https://github.com/nodejs/node/actions/runs/6191368639/job/16809521748?pr=49657.) Refactoring the modules code shouldn’t break these unrelated tests; these snapshots should be like the others that exclude detailed stack traces of modules internals. These two specific cases probably slipped through because they’re edge cases, having to do with source maps and colored stack trace output. This PR updates the tests and snapshots so that future modules changes don’t break these tests. @nodejs/test_runner @nodejs/testing

Merge request reports

Loading