Support environments for shareable configs

I would like to keep my shareable config similarly to package.json field “browserslist”, like this:

module.exports = {
  development: ['last 2 chrome versions', 'last 2 firefox versions', 'last 2 edge versions'],
  production: [
    '>1%',
    'last 3 versions',
    'not dead',
    'not op_mini all',
    'Firefox ESR',
    'not ie < 11',
  ],
};

For now it’s impossible because of error: config exports not an array of queries .

[sybrendotinga]

I was experimenting with implementing a shareable config for our company today. Because we also have two environments in our current setup I was looking into how to implement this. I ended up in this topic. For us this is a great use-case aswel. For now, I decided to only implement the production environment, that will also be used in our development environment.

We would like to use this feature as @JamiesonRoberts describes it. It would be great to have a base configuration, but also have the option to override rules for a specific project.

[ai]

How often is this file read? What is the impact of not having it cached?

If we will use JS file, webpack/Parcel will not be sure that the content of the file was not changed.

It certainly shouldn’t be FORCING security related decisions.

I believe that every software should think about security.

Any your dependency can be used to hack the system. If a tool can potentially be used with non-trused user input, it is a security tool.

For now, I’ll hold off on a PR until we can come to a consensus.

This issue is about adding environments to shared config.

Removing mandatory browserslist-config prefix or adding JS-based config should be discussed in separated issue.