reactjs / reactjs/react.dev

[Framework]: Meteor.js

未关闭
#8,477 0 条评论 11 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

主要语言
JavaScript
星标
11.8k
派生
7.9k
平均合并
1 天 11 小时
30 天内合并 PR
11

描述

Applying to have Meteor.js considered as a recommended React framework. Submitted by a Meteor contributor.

Name

Meteor.js

Homepage

https://www.meteor.com

Install instructions

https://docs.meteor.com/tutorials/react/

Is your framework open source?

Yes — MIT licensed.

Well maintained

Meteor has been developed continuously since 2012 and is actively maintained by Meteor Software. The most recent major milestone, Meteor 3.0, was a full rewrite of the server runtime that removed Fibers in favor of native async/await on modern Node.js. The 3.x line ships regular releases (currently 3.5, in RC) with ongoing fixes and improvements. Development happens fully in the open at https://github.com/meteor/meteor with a public changelog and roadmap.

Active community

Meteor is a long-standing, widely adopted project — 44,000+ GitHub stars and 5,200+ forks (https://github.com/meteor/meteor), in continuous development since 2012. Signals of an active, real-world user base:

Clear onboarding

Creating a React app takes two commands:

npx meteor            # install
meteor create my-app  # React is the DEFAULT skeleton (or pass --react)
cd my-app && meteor

The generated project is a React + Meteor app out of the box. Reactive Meteor data is consumed from React via the react-meteor-data package (useTracker, useFind, useSubscribe hooks). Guide: https://docs.meteor.com/tutorials/react/

Ecosystem compatibility

Meteor apps are standard npm projects — any npm package works, including the full React ecosystem (React Router, component libraries, state managers). Meteor 3 builds the client with a modern Rspack/SWC pipeline. Meteor also offers optional Atmosphere packages for integrated full-stack features (accounts, pub/sub), but these are additive — plain React libraries work unchanged. The one caveat: Meteor provides its own integrated build system rather than exposing an external bundler config.

Self-hosting option

Fully self-hostable with no feature loss. meteor build produces a standard Node.js bundle that runs anywhere Node + MongoDB are available (bare Node, Docker, Meteor Up/mup, any PaaS). A managed option (Galaxy) exists but is entirely optional. In full transparency: Meteor is server-first — it requires a running Node.js server and MongoDB, and does not target static/CDN-only deployment, because its core value is a real-time data layer over a persistent connection (DDP).

Developer Experience

A single meteor command runs the app with live reload and React Fast Refresh (via react-refresh / @rspack/plugin-react-refresh in the React skeleton), preserving component state across edits. It's plain React on the client, so React DevTools and Chrome DevTools work normally. An integrated build and a built-in development MongoDB mean there's no separate bundler/config to wire up.

User Experience

Meteor's differentiator is a built-in, end-to-end reactive data layer: publications/subscriptions (DDP) stream live data, Minimongo gives optimistic UI updates, and Methods provide RPC — solving data-fetching and real-time sync without hand-written APIs or client/server waterfalls for live data. It includes a full accounts system, build-time code splitting, and SSR via the server-render package. Routing is not in core (apps use React Router or a community router). The model is optimized for real-time, stateful apps rather than SSG.

Compatible with our future vision for React

Meteor does not currently implement React Server Components; its full-stack model is built on Meteor's own reactive primitives (DDP, Minimongo, Tracker) rather than the RSC/Suspense data path. That said, Meteor consistently modernizes alongside the ecosystem — Meteor 3 removed Fibers for native async/await and moved the build to Rspack/SWC — and we're keen to collaborate with the React team on how Meteor can adopt and align with React's server-first direction (RSC, Suspense for data fetching) over time.

贡献指南

打开贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

调研方向

未指定任何仓库文件、测试或入口点。首先查找 react.dev 目前如何评估或推荐 React 框架,然后查看贡献指南和现有的框架条目。完成标准是由维护者批准一项关于 Meteor.js 的决定;如果接受该决定,则添加推荐内容和支持链接。

由索引模型根据 Issue 内容生成。

评估

技术栈
javascript, mongodb, node.js, react
领域
documentation, web-dev
Issue 类型
功能
难度
5/5
预计耗时
一周以上
活跃度
冷清
描述清晰度
基本清楚
新手友好度
35/100

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。