Nitin Kumar
Nitin Kumar
I'll check this
We do have similar plans as mentioned in https://github.com/webpack/webpack-dev-server/issues/4303. However, this is not yet prioritized. We will gladly accept a PR.
I'll fix it
Sure, I'll update in webpack
Yes, we use `interpret` in webpack-cli.
> since env param in the cli is already taken, what should we use for passing array of env file names in the cli? does env-file work? @burhanuday I didn't...
I'll check the CI
I agree, showing add on top would shift the content below leading to a degraded UX. Maybe we can do something similar to [ESLint](https://eslint.org/docs/latest/use/configure/configuration-files), it moves the ad to the...
Thanks for the PR, but this change is unnecessary here.
Using `[name]` within `output.library`, the correct value isn't utilized in the source map namespace
> Currently we are generating sources is constructed with [uniqueName](https://github.com/Nightrider0098/webpack/blob/c586c7b1e027e1d252d68b4372f08a9bce40d96c/lib/config/defaults.js#L860). Either we need to use some other variable this is later parsed with getAssetPath or we need to update the...