config file json js ts support

Would you consider to support browserslist.config.json and even browserslist.config.js browserslist.config.ts as config files?

I am currently gathering some information and opinions about config files and conventions and wrote a short article about the the inconsistency that is going on at the moment and a proposal as a possible solution. What are your thoughts on this?

[timreichen]

I see. I am very glad to hear that it would be at least a considerable. In my opinion the support for the JSON format on it’s own would already be a huge deal. As described in my article I am not a big fan of using package.json for configuration data, allowing a self contained browserslist.config.json would make a big difference and has some real use cases:

• Simpler dynamic config file generation
• Easy parsing format (for example in plugins)
• Paves the way to easy support for other tools like deno who do not have a package.jsonfile and use JSON as a standard config format (as in tsconfig.json)
• Aligns with lots of other tools (webpack, parcel, rollup, babel, deno, import-maps etc.) and therefore going in a more standardised direction
• Would allow for IntelliSense in VSCode

[dev99problems]

Hey folks, any updates on that? TBH this is really a pain in the ass in case of monorepo, when you want to share a bunch of configs for different tools, but you have to implement a separate package specifically for BL shareable config. Looks like a some hack.

1. I like to allow other languages to parse Browserslist. For instance, in Autoprefixer Rails I use Ruby code to parse the file. In the past Compass parsed it as well.

Totally agree on that, so seems like for other languages default browserslistrc fits perfectly, but for a such heavily relied package as Browserslist in front-end community it would be extremely helpful to support some implicit common practice, like giving the ability to set up configuration in js file, etc.