{"id":13790154,"url":"https://github.com/nuxt/rfcs","last_synced_at":"2025-10-19T08:32:13.452Z","repository":{"id":65982873,"uuid":"154654688","full_name":"nuxt/rfcs","owner":"nuxt","description":"RFCs for changes to Nuxt.js","archived":false,"fork":false,"pushed_at":"2023-12-15T14:27:57.000Z","size":8,"stargazers_count":98,"open_issues_count":9,"forks_count":2,"subscribers_count":35,"default_branch":"master","last_synced_at":"2025-01-29T11:11:35.672Z","etag":null,"topics":[],"latest_commit_sha":null,"homepage":"","language":null,"has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":null,"status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/nuxt.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":null,"funding":null,"license":null,"code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null}},"created_at":"2018-10-25T10:48:30.000Z","updated_at":"2024-12-11T20:31:10.000Z","dependencies_parsed_at":"2024-08-03T22:12:53.473Z","dependency_job_id":null,"html_url":"https://github.com/nuxt/rfcs","commit_stats":null,"previous_names":[],"tags_count":0,"template":false,"template_full_name":null,"repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/nuxt%2Frfcs","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/nuxt%2Frfcs/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/nuxt%2Frfcs/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/nuxt%2Frfcs/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/nuxt","download_url":"https://codeload.github.com/nuxt/rfcs/tar.gz/refs/heads/master","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":237092921,"owners_count":19254308,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":[],"created_at":"2024-08-03T22:00:37.798Z","updated_at":"2025-10-19T08:32:12.310Z","avatar_url":"https://github.com/nuxt.png","language":null,"funding_links":[],"categories":["rtfs","Others"],"sub_categories":["redux 扩展"],"readme":"# Nuxt 3 RFCs\n\n👉 https://github.com/nuxt/nuxt/discussions/categories/rfcs\n\n# Nuxt.js RFCs\n\nMany changes, including bug fixes and documentation improvements can be\nimplemented and reviewed via the normal GitHub pull request workflow.\n\nSome changes though are \"substantial\", and we ask that these be put\nthrough a bit of a design process and produce a consensus among the Nuxt.js\ncore team.\n\nThe \"RFC\" (request for comments) process is intended to provide a\nconsistent and controlled path for new features to enter the project.\n\n## When to follow this process\n\nYou should consider using this process if you intend to make \"substantial\"\nchanges to Nuxt.js or its documentation. Some examples that would benefit\nfrom an RFC are:\n\n   - A new feature that creates new API surface area, and would\n     require a feature flag if introduced.\n   - The removal of features that already shipped as part of the release\n     channel.\n   - The introduction of new idiomatic usage or conventions, even if they\n     do not include code changes to Nuxt.js itself.\n   - Introducing new core packages\n\nThe RFC process is a great opportunity to get more eyeballs on your proposal\nbefore it becomes a part of a released version of Nuxt.js. Quite often, even\nproposals that seem \"obvious\" can be significantly improved once a wider\ngroup of interested people have a chance to weigh in.\n\nThe RFC process can also be helpful to encourage discussions about a proposed\nfeature as it is being designed, and incorporate important constraints into\nthe design while it's easier to change, before the design has been fully\nimplemented.\n\nSome changes do not require an RFC:\n\n  - Rephrasing, reorganizing or refactoring\n  - Addition or removal of warnings\n  - Additions that strictly improve objective, numerical quality\n  criteria (speedup, better browser support)\n  - Additions only likely to be _noticed by_ other implementors-of-Nuxt.js,\n  invisible to users-of-Nuxt.js.\n\n## What the process is\n\nIn short, to get a major feature added to Nuxt.js, one usually creates an issue that will be labled with 'active' when approved by core team. At that point the RFC\nis 'active' and may be implemented with the goal of eventual inclusion into Nuxt.js.\n\n## The RFC life-cycle\n\nOnce an RFC becomes active, then authors may implement it and submit the\nfeature as a pull request to the Nuxt.js repo. Becoming 'active' is not a rubber\nstamp, and in particular still does not mean the feature will ultimately\nbe merged; it does mean that the core team has agreed to it in principle\nand are amenable to merging it.\n\nFurthermore, the fact that a given RFC has been accepted and is\n'active' implies nothing about what priority is assigned to its\nimplementation, nor whether anybody is currently working on it.\n\n## Implementing an RFC\n\nThe author of an RFC is not obligated to implement it. Of course, the\nRFC author (like any other developer) is welcome to post an\nimplementation for review after the RFC has been accepted.\n\nIf you are interested in working on the implementation for an 'active'\nRFC, but cannot determine if someone else is already working on it,\nfeel free to ask (e.g. by leaving a comment on the associated issue).\n\n## Reviewing RFCs\n\nEach week the team will attempt to review some set of open RFC\npull requests.\n\nWe try to make sure that any RFC that we accept is accepted at the\nweekly team meeting. Every accepted feature should have a core team champion,\nwho will represent the feature and its progress.\n\n**Nuxt.js's RFC process owes its inspiration to the [React RFC process], [Yarn RFC process], [Rust RFC process], and [Ember RFC process]**\n\n[React RFC process]: https://github.com/reactjs/rfcs\n[Yarn RFC process]: https://github.com/yarnpkg/rfcs\n[Rust RFC process]: https://github.com/rust-lang/rfcs\n[Ember RFC process]: https://github.com/emberjs/rfcs\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fnuxt%2Frfcs","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fnuxt%2Frfcs","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fnuxt%2Frfcs/lists"}