Skip to content

Shareable Configs #2748

@jhanikhilnath

Description

@jhanikhilnath

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

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions