Feature: Show which runtimes need or don't need plugins
- Dominant language
- TypeScript
- Stars
- 777
- Forks
- 1.4k
- Avg merge
- 16h 45m
- Merged PRs (30d)
- 3
Description
## Overview
Today, plugin pages say what presets plugins are included in and link to a few docs such as TC39 proposals. For example, https://babeljs.io/docs/babel-plugin-transform-class-properties:
* Mentions it's in the ES2022 preset
* Links to [Proposal: Public and private instance fields](https://github.com/tc39/proposal-class-fields) and [Proposal: Static class features](https://github.com/tc39/proposal-static-class-features)
...but the pages never explicitly say what runtimes (e.g. browsers / Node.js / other server runtimes) do or don't need the plugins. This means it can be hard for folks who aren't deeply entrenched in the JS ecosystem to know whether they need a plugin.
Proposal: could plugin pages have some kind of compatibility indicator added? Perhaps an indication of which common browser, Bun, Deno, and LTS Node.js versions support the feature?
### Additional Information
MDN does the equivalent of this really nicely on their docs. For example, https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Classes/Public_class_fields:
* Mentions it's baseline widely available at the top of the page, with links to more info
* Shows the browser & runtime support versions at the bottom of the page
@nicolo-ribaudo pointed me towards https://github.com/babel/babel/blob/main/packages/babel-compat-data/data/plugins.json as already having info on support targets.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.