reactjs / reactjs/react.dev

[Framework]: Meteor.js

オープン
#8,477 コメント 0 件 リアクション 11 件 担当者 0 名 GitHub で見る

まだ誰も着手していません。

主要言語
JavaScript
スター
11.8k
フォーク
7.9k
平均マージ
1日 11時間
マージ済み PR(30日)
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. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

調査の方向性

リポジトリのファイル、テスト、エントリーポイントのいずれも指定されていません。まず、現在 react.dev が React フレームワークをどのように評価または推奨しているかを調べ、次にコントリビューションガイドラインと既存のフレームワーク項目を確認してください。完了条件は、Meteor.js についてメンテナーが承認した判断がなされ、採用された場合に推奨内容と根拠となるリンクが追加されていることです。

索引モデルが issue の本文から書いたものです。

評価

技術スタック
javascript, mongodb, node.js, react
領域
documentation, web-dev
issue の種類
機能追加
難易度
5/5
見積もり時間
1週間以上
活発さ
静か
明瞭さ
おおむね明確
初心者へのやさしさ
35/100

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。