CodeVetter · Repo Unpack · Feature catalog
meteor/meteor
The inspected user-facing surface combines CLI workflows with APIs used inside Meteor applications. Developers can scaffold multiple frontend stacks, run web/mobile targets, manage dependencies and platforms, build standalone artifacts, and request hosted deployment. Application authors receive reactive data replication, HTTP extension hooks, and password-based authentication.
- meteor create supports package creation, named examples, source repositories/branches/subdirectories, and skeleton options including React, Vue, Svelte, Solid, Angular, TypeScript, Blaze, and Tailwind.
- meteor run accepts additional run targets, extra packages, production-simulation mode, settings, architecture filtering, and optional browser opening; mobile targets trigger Cordova preparation unless disabled.
- meteor build calls bundler.bundle with selected server/web architectures and development or production modes, then emits either a bundle directory or a compressed server tarball.
- meteor deploy exposes deletion, settings, deployment token, owner, Mongo provisioning, plan/container size, cached builds, build-only mode, and optional deployment waiting.
- meteor add requires an application and splits arguments into Meteor packages and Cordova plugins; plugin specifications accept exact versions, Git URLs with SHA references, or local paths.
- add-platform and remove-platform prepare bundled dependencies before changing Cordova platforms; list-platforms reads and prints ProjectContext's installed platform list.
- Applications register DDP methods and named or universal publications, while WebApp exposes application/raw HTTP handlers and an overridable startListening function.
- Runtime APIs include asynchronous password login and 2FA login, Mongo.Collection.insertAsync, replicated document updates, and Tracker.Dependency-based reactive invalidation.