Ivan Kopeykin

> What you're saying only worked if you used something along the lines of DefinePlugin({'process.env':{NAME: 'foo'}}) that is a correct usage.. not sure what you mean.. ------------------------------ if you define...

yes, api is not optimal, but breaking change could lead to security leaks like: webpack.config.js ```js const define = new DefinePlugin({'env': {..blabla}, 'env.SECRET': 1}); module.exports = [{ name: 'my-awesome-backend', entry:...

@alexander-akait what do you think about this PR? should we somehow define unique name in this case?

@alexander-akait fixed. As I understand cache does not work correctly with same `name`, so `name` always should be unique

fixed @alexander-akait

@dmichon-msft thats not possible.. the hole idea is that you can plug-in/plug-out plugins..

with `then` it is very tricky. we definitely could not support all cases. I thought about async/await support or simply -> only assigning support, like: ```js import * as ns...

@TheLarkInn because of javascript complexity: ```js const a = import('a'); a.then(({b}) => {}); a.then(({c}) => {}); // this will work I guess a.then(v => { const {c} = v; return...

I think this is valid, `ignoreWarnings` should be respected.

need to think about this carefully.. idea of `environment` option is to understand does environment support some features ( basically js features now ). Maybe store additional target information? so...