Randall Leeds
Randall Leeds
I had some good success reconfiguring a project to use only babelOptions to supply rootMode upwards and everything else configured in babel.config.js. Configuring just root to be __dirname from eslint...
If, instead of wrapping `reason` with `new AbortError(..., { cause: signal.reason })`, Node.js followed `fetch` in throwing `reason` itself, wouldn't `error === signal.reason` work to detect cancellation?
@benjamingr I think this is a better place to respond to your comment about fetch[^1] than on the closed issue for that, but please direct me if there's a more...
No rush on any fuller response, but I'll leave my reactions for when you return: > I think breaking the way everyone checks errors everywhere is a huge breaking change...
Maybe consider https://github.com/nodejs/undici
If you can provide more information for debugging or a case to reproduce the problem, please open a ticket with details. Thanks!
That is very strange. I'll re-open the issue. Please continue investigating if you can.
If you can publish a repository with setup instructions to reproduce this that would be the best.
I have not yet had a chance to look.
I like this PR. I'm sorry I missed it before. I want to be sure it works correctly and haven't had a chance to test. My argparse knowledge is weak,...