Emilio Martinez

Just ran into this issue while trying to upgrade to Webpack 4.x—I have a lib that is for any env. Looking at my previous releases, `window` used to be in...

It looks like `self` is `Window` in browserland but is `undefined` in `node` anyway. Not sure if `this` is the global for workers.

On that note, documenting that options passed to `babel-loader` will pretty much take precedence over those in `babel.config.js` or `.babelrc` would be great to have documented. I spent about an...

@jhusain If I may, I believe you're nitpicking a bit too much on that point. First, the benefits and ergonomics of having the listener removed due to the first() operator...

I'm also getting those warnings about `@babel/plugin-proposal-private-private-property-in-object` – does anyone have insight on that `@babel/preset-env`-related issue and know if it's relevant?

@AndyOGo people _could_ use those, but I guess the question is—what does that mean for this project? Patching built-ins could remain an add-on to the baseline custom elements polyfill, but...

To second @lummax, I think it would be awesome if Bazel could support yarn berry, which I'd consider as the only actively maintained version at the time of this writing....

@vire I don't know that this is an issue with this plugin or Webpack. When you're building without any progress plugin, you'll see that Webpack increases resolved dependencies to its...

@jacob-ebey is there a design doc somewhere that specs module federation and how different bundlers need to interop? I'm interested in this, and may even contribute, but webpack MF features...

@radoering please do consider moving it to a plugin 🙏 saying it having seen first-hand how much easier it is for engineers (with varying degrees of python comfort) to switch,...