Will Binns-Smith

@shuding this breaks the "On this page" section on the right because these aren't headings managed by Nextra (they're not markdown headings). Any suggestions to get these featured? Was thinking...

> `node:fs` is also considered as URL request Yeah, this is a good point. We'll want to treat this the same way we do other external requests in node, and...

😍😍😍 Whitelist and blacklist sounds awesome. I wonder if it could even be a shared resource (published to npm itself?). For example has similar behavior for `yarn create`. @js-n, something...

If it helps, I've also set up [a small repository](https://github.com/wbinnssmith/rewire-babel-conflict) demoing the conflict. Just run webpack and load the resulting bundle in a script tag to see the issue.

@calebmer landed ab0789a today, which I believe should make it out with the next release of flow. I know I personally can't wait to use it 🎉 thanks @calebmer!

I can confirm that I get this error when using rewire-webpack with the babel-loader (5.x or later, 4.x is just fine). My guess is that this, #12, and #11 are...

I'm also having this exact issue, and this patch resolves it. Any chance it will be merged? Would be much appreciated!

Closing in favor of the link and docs added in #2492.

> This also switches from the default FSEvents implementation to the new inotify-based implementation, which I've measured to be significantly faster. Nit: do you mean kqueue here? I think inotify...

Current dependencies on/for this PR: * main * **PR #2743** * **PR #2742** 👈 * **PR #2769** * **PR #2812** * **PR #2856** * **PR #2940** This comment was auto-generated...