reactjs / reactjs/react.dev

[Framework]: Meteor.js

Ouverte
#8,477 0 commentaires 11 réactions 0 personnes assignées Voir sur GitHub

Personne n'a encore pris cette issue.

Langage dominant
JavaScript
Étoiles
11.8k
Forks
7.9k
Merge moyen
1 j 11 h
PR mergées (30 j)
11

Description

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.

Guide de contribution

Ouvrir le guide de contribution

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Piste de recherche

Aucun fichier du dépôt, test ou point d’entrée n’est indiqué. Commencez par déterminer comment react.dev évalue ou recommande actuellement les frameworks React, puis examinez les consignes de contribution et les entrées de frameworks existantes. Le travail est terminé lorsqu’une décision approuvée par un mainteneur concernant Meteor.js a été prise, avec l’ajout de la recommandation et des liens justificatifs si elle est acceptée.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Évaluation

Stack technique
javascript, mongodb, node.js, react
Domaine
documentation, web-dev
Type d'issue
Fonctionnalité
Difficulté
5/5
Temps estimé
Plus d'une semaine
Activité
Calme
Clarté
Plutôt claire
Accessibilité débutants
35/100

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.