Results 1 comments of MattC

I encountered this issue due to: - A transition from yarn@v1 -> yarn@v3 - Stale nested `node_modules` directories leading to Node.js using the incorrect (older) version of `http-errors`. What worked...