vuejs/rfcs resource
RFCs for substantial changes / feature additions to Vue core observed · 2026-08-28
Health v2 · maintenance only
32/100
- Activity 0
- Release rhythm 35
- Longevity 100
Flags: no_releases no_license
How is this computed?
round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-03. Adoption (stars, forks) is never an input.
- gap_med: n/a
- age_days: 2823
- days_rel: n/a
- days_push: 602
- n_releases_24m: 0
Adoption not part of the score
4938 stars · 537 forks observed · 2026-08-28
What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-29, confidence not recorded
The official RFC (request for comments) repository for Vue core, documenting the design process for substantial feature additions and API changes. It tracks proposals through pending, active, landed, and rejected lifecycle stages.
Use cases
- propose a new feature to Vue core
- understand how Vue 3 APIs were designed
- track the status of an upcoming Vue feature
- learn how a framework RFC process works
- find rationale behind Vue API decisions
When to choose
- you want to contribute a substantial change to Vue core
- you want to read design discussions behind Vue features
- you want to follow upcoming Vue API changes
When to avoid
- you need Vue runtime code or libraries
- you want to propose changes to Vue ecosystem projects other than core
- you need bug fixes or documentation improvements, which use normal PRs
Facets
learning-resource · maturity active
documentation web-development frontend programming-languages rfcs vue design-process governance community web-server
1 source
- readme: https://github.com/vuejs/rfcs · fetched 2026-08-28 · c96158e83e9f
Member repositories
| Repository | Role | Health v2 |
|---|---|---|
| vuejs/rfcs | main | 32 |
For agents
Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem