webpack
Shareable Configs
Feature request
What is the expected behavior? Having shareable configs
What is motivation or use case for adding/changing the behavior? We have to write webpack configs every time we start a new big project. Which is usually twice or thrice a year. So, having shareable configs would be very useful.
How should this be implemented in your opinion? Just like in eslint
module.exports = {
extends: ["shareable config name"]
}
Are you willing to work on this yourself? No. I don't have the skills for it. I am a learning developer
P.S: My english is not very good as it is not my first language
Please use this package to achieve this https://github.com/survivejs/webpack-merge. Also you can publish package (common configuration) and require/import it in your new package. Webpack configuration can be complex and there is no single strategy on how best to do it - some options better to merge, other to override.
I think the same behavior can be achieved through --merge. But if we want it to be an option in config we will need to update webpack schema.
Yep, right direction, In theory we can require/import from extends and apply webpack-merge, we don't need update schema, because we remove extends from webpack.config.js internally, we need update only types, but it is not hard
@snitin315 Don't forget extended configuration can have extends too, so we need do it in loop until we have extends
I am very confused as to what is happening as this is my first issue in github Can someone summarise everything
Can someone summarise everything
We will implement this feature request in the near future 😄
Seriously I can’t believe that my first feature request on github is being implemented
This issue had no activity for at least half a year.
It's subject to automatic issue closing if there is no activity in the next 15 days.
Issue was closed because of inactivity.
If you think this is still a valid issue, please file a new issue with additional information.