[RFC][lab] Next steps for the `@mui/lab` package
Open
@DiegoAndai is already working on this.
Since Jan 18, 2024.
package: lab
RFC
scope: all components
- Dominant language
- JavaScript
- Stars
- 99.1k
- Forks
- 32.5k
- Avg merge
- 2d 17h
- Merged PRs (30d)
- 106
Description
What's the problem?
The @mui/lab package is not getting enough attention, and there's no process to move the components to stable or decide to remove them. This ends up in inferior DX for users.
What are the requirements?
- Components are not to be abandoned, as that would worsen the experience for the components' users.
What are our options?
- Continue with the package and set up a process for promoting or removing components.
- Remove the package and decide what to do with each component.
Proposed solution
Remove the package and decide what to do with each component. The options are:
- Move to a stable package and mark them as unstable
- Prepare for stable release and move to a stable package
- Deprecate it in favor of something else and provide a migration guide
Search keywords: lab rfc
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.