Support creation of .browserslistrc

[sdavids]

Some options:

$ npx browserslist-config-baseline --write
$ npx browserslist-config-baseline --write /some/path/.browserslistrc

$ npx browserslist-config-baseline --dump-configuration >.browserslistrc

$ npx browserslist-config-baseline --resolved-query >.browserslistrc
$ npx browserslist-config-baseline --resolved-query --baseline-year 2022 --with-downstream >.browserslistrc

[tonypconway]

Hey Sebastian, thanks for raising this. Is there a particular reason you'd rather have minimum browsers in a .browserslistc file rather than generated on the fly?

We did discuss doing this in the past as part of #5 and we weren't sure if it was a good idea because you'd end up with a static list rather than one that moves with Widely available (the default target for this module). You might also end up with some data staleness if you're using downstream browsers. Or would you anticipate running this every time you build, for example?

One option you already have is creating your own small script that uses baseline-browser-mapping and writes to your own .browserslistrc file. As an example, the Angular team are planning to do this in the next version of Angular.

[sdavids]

As far as I am aware, some tools do not evaluate package.json for the query; they use .browserslistrc.

Also, if you go with npx browserslist-config-baseline --resolved-query or something similar one can also check what is actually configured.

You might also end up with some data staleness if you're using downstream browsers.

This is mainly for the "pinned to specific year" use case.

[tonypconway]

You can also put extends browserslist-config-baseline in .browserslistrc - as in these examples.

browserslist-config-baseline will still respect your package.json settings, so if you set:

"browserslist-config-baseline" : {
  "logConfigToConsole": true
}

Then you'll see the browserslist config every time the module is called. Running npx browserslist will also work in this context, giving you the resolved query.

Does this cover your use case?

[sdavids]

$ jq .browserslist,".[\"browserslist-config-baseline\"]" package.json 
[
  "extends browserslist-config-baseline"
]
{
  "baselineYear": 2022,
  "logConfigToConsole": true
}
$ npx browserslist >/tmp/.browserslistrc
$ cat /tmp/.browserslistrc
Your browserslist config from browserslist-config-baseline is:
 [
  'Chrome >= 108',
  'ChromeAndroid >= 108',
  'Edge >= 108',
  'Firefox >= 108',
  'FirefoxAndroid >= 108',
  'Safari >= 16',
  'iOS >= 16'
]
and_chr 135
and_ff 137
chrome 136
chrome 135
chrome 134
chrome 133
chrome 132
chrome 131
chrome 130
chrome 129
chrome 128
chrome 127
chrome 126
chrome 125
chrome 124
chrome 123
chrome 122
chrome 121
chrome 120
chrome 119
chrome 118
chrome 117
chrome 116
chrome 115
chrome 114
chrome 113
chrome 112
chrome 111
chrome 110
chrome 109
chrome 108

instead of:

chrome>=108,and_chr>=108,edge>=108,firefox>=108,and_ff>=108,safari>=16,ios_saf>=16

[SHORIF393]

Join