feat: initial implementation of browserslist-plausible

[SethFalco]

I've created this repository in hopes to transfer it to github.com/browserslist. Keep that in mind while reviewing. Meanwhile, I'll explain all of my decisions.

See: https://github.com/orgs/browserslist/discussions/911

Stack

Uses JavaScript with JSDoc types for type checking.

While you'll see typescript in the dependencies and a tsconfig.json file, this project is not written in TypeScript. A type checker is just used to validate the JavaScript types in CI. No transpilation is necessary. 💪(•ᴗ•💪)

Implementation

I originally planned to support CSV exports, but dropped it. After reviewing this more critically, I realized it's not as practical as the API.

If a user in the real-world finds they need support for CSV exports, we can add this reactively, but I won't do this eagerly since it just provides less accurate data. It's not necessary for v1 anyway.

Implementation Detail

CLI Arguments

I named the --outputPath argument as such to match browserslist/browserslist-ga-export. Fairly arbitrary, but should feel more intuitive if someone is migrating over or maintaining both.

Browser Matching

I did not use the browserslist/map-to-chrome because:

• It's very outdated anyway.
• I actually couldn't! I tried, but the exports seem funny. I couldn't import anything, perhaps because I wrote this as ESM instead of CJS.

So unfortunately, browsers like Yandex are not mapped to Chrome versions! We can revise this in future if we could update the browserslist/map-to-chrome project.

Consistency with other Browserslists repositories

I used pnpm as I can clearly see from the other repositories Browserslist uses pnpm for most of their other projects. This should make it more comfortable to maintain/publish for other org members.

I also used the MIT license for the same reason, as Browserslist uses it for most other repositories, and I'm cool with it.

GitHub Actions

I've added two:

• Quality Assurance (unit tests, type checking JSDoc types, spellchecking, etc)
• Publishing to npm via Trusted Publisher Workflow, though an npm package doesn't currently exist.