clean-stack

is not always idempotent. This PR fixes it. The reason is: any stack line that looks like is filtered out but the option produces such lines, _providing_ the file is directly in the directory (not a subdirectory) So, when the option is used, applying a second time results in an empty stack trace. The problem here is: why remove stack lines that look like ? It seems like this originated from the following commit 9 years ago: https://github.com/sindresorhus/clean-stack/commit/571de7fe5cce8574df2e971ea30c01f64974cc2d If I'm not mistaken, it seems like the reason was to remove the stack lines that were added by Node.js when executing a shebang file. However, those lines are not produced since Node.js 10. Another potential reason might be to remove node internals which used to be like: . However, since Node 10, those are like: . Then since Node 16, the stack shows instead of . 's regular expression targets both the and the keywords, so there's no need for the above logic then, if that was the reason.