Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Proposal for Metro plugin architecture #1290

Open
afoxman opened this issue Mar 20, 2022 · 0 comments
Open

Proposal for Metro plugin architecture #1290

afoxman opened this issue Mar 20, 2022 · 0 comments
Labels
feature: metro This is related to Metro

Comments

@afoxman
Copy link
Contributor

afoxman commented Mar 20, 2022

Working with the Metro team, jointly develop plans for a Metro plugin architecture. Focus on a few "hero" plugins from webpack which have broad appeal and use them to frame the design.

Should it be limited? Or should it be broad enough to support much of the webpack ecosystem (with appropriate adapters)?

The underlying premise is that having plugins will accelerate new capabilities for Metro. Upstreaming to main requires more time and rigor, and exposes everyone to the changes. Plugins are localized to only devs that use them. The tradeoff is that quality may be lower, and Metro performance and caching may suffer as a result.

Output is a jointly acceptable proposal.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature: metro This is related to Metro
Projects
Status: 🌳 Backlog
Development

No branches or pull requests

2 participants