meteor/agent-skills

meteor-cli-installation

Use when installing, locating, repairing, resetting, or uninstalling the Meteor CLI for Meteor 3 development.

소스 보기

사용 방법

  1. 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
  2. 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
  3. 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
npx skills add https://github.com/meteor/agent-skills --skill meteor-cli-installation

시작 전 확인

  • 설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
  • 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 Skill 문서

원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.

Install and repair the Meteor CLI

Make the Meteor CLI available without changing an application or deleting state that the user did not place in scope. npx meteor runs the official npm installer and creates a user-wide Meteor installation; it does not add the installer permanently to global npm packages.

Decision flow

  1. Classify the request before changing the machine.
  • Install a missing CLI when the user asks to set up Meteor or requests a

local create, run, test, build, or deploy operation that requires it.

  • For explanation, review, or planning only, report the missing prerequisite

and the install command without running it.

  • Require explicit confirmation before any recovery operation that removes

state: meteor reset, meteor reset --db, npm cache clearing, targeted global metadata cleanup, uninstall, or full reinstall.

  • When evidence makes a cleanup or reinstall plausible, suggest the least

destructive option with its reason, scope, and expected state loss. Do not execute it until the user explicitly confirms that operation.

  1. Inspect the host and intended project. Check the operating system,

architecture, node --version, npm --version, CLI lookup result, and meteor --version when available. In an application, read .meteor/release before selecting a release.

  1. Distinguish the requested version:
  • The npm selector in npx meteor@<version> chooses an installer package.
  • A Meteor application is pinned to a framework release in

.meteor/release. Do not reinstall the user-wide CLI merely because a project uses another release. Before selecting Meteor 3.6-beta.3 or 3.6-rc.0 for existing local data, read local database preparation. Its bundled MongoDB 8 requires host checks and MongoDB 7 FCV preparation under the previous release before the new release starts.

  1. For a missing CLI, PATH failure, npm installer failure, or host

prerequisite, follow Installation and PATH.

  1. For a project release, cache reset, corrupted dev bundle, uninstall, or

clean reinstall, follow Releases, reset, and reinstall. Use Reinstall decision guide before recommending a user-wide reinstall for an observed failure.

  1. Verify the result with meteor --version. For project work, run the

narrowest requested Meteor command and confirm that it resolves the release in .meteor/release. Report commands run, selected versions, state removed, and anything the user must do in a new shell.

Installation rules

SituationAction
Latest supported CLIRun npx meteor.
Pinned installer packageRun npx meteor@<version> install, then verify the reported Meteor release.
Linux or macOS alternative`curl https://install.meteor.com/ \sh remains documented. Keep npx meteor` as the primary cross-platform command.
npm fallbackRun npm install -g meteor --foreground-script only after the documented npx recovery steps fail.
Existing project needs another releaseUse the project's pin or a Meteor --release command. Do not replace the user-wide installation first.

Never run npx install meteor. Never add the npm meteor installer to an application's package.json; it is an installer, not the framework runtime.

State boundaries

StateScopeSafe operation
User Meteor directoryDownloaded tools, releases, dev bundles, and CLI state for the usernpx meteor uninstall removes the whole installation. Use only for an authorized uninstall or clean reinstall.
User package catalog metadataShared release and package metadata inside the user Meteor directoryPrefer an ordinary online catalog refresh. Treat targeted metadata rebuilding as an advanced, confirmation-required recovery.
.meteor/releaseProject framework releaseChange through meteor update --release <release>, not a global reinstall.
.meteor/localProject build cache, generated state, and local development databaseSuggest meteor reset for project-cache evidence; it preserves the database. meteor reset --db deletes it. Run either only after confirmation.
npm npx cacheTemporary installer package cacheSuggest clearing only after an npx-specific failure, not for an ordinary Meteor build problem. Run only after confirmation.

Do not delete internal tool or dev-bundle directories selectively without a documented command and evidence that identifies that layer. Use meteor reset for project cache corruption. Use a complete, authorized reinstall only when the user-wide installation itself is corrupt. Never recommend hidden Meteor administration commands as user-facing cache cleaners.

Handoffs

  • The CLI starts but the application fails: meteor-debugging.
  • The application must move from Meteor 2 to Meteor 3: migrate-to-meteor-3.
  • A build cache or bundler failure remains after the CLI and project state are

classified: meteor-modern-build-stack or migrate-to-rspack.

  • Deployment credentials, Galaxy, containers, or runtime configuration:

meteor-deployment.

References

관련 작업

같은 저장소의 Skills

더 많은 Skills

모든 Skills
meteor
커뮤니티

meteor-debugging

Use when diagnosing an unexplained failure in a Meteor 3 application before the failing layer or fix is known. Triggers on server crashes, client-only errors, stuck subscriptions, DDP or WebSocket disconnects, Minimongo/server data mismatches, hanging or flaky tests, slow builds, --inspect, console.log, .only, Playwright traces, Instrumentation lifecycle events, or requests to debug a Meteor app. Use this skill when evidence must distinguish Meteor tool, server, client, data, test, browser, mobi

1시간 설치 수
1
GitHub Stars
10
업데이트
10월 14일
meteor
커뮤니티

meteor-methods

Use when authoring or debugging Meteor methods (Meteor.methods, Meteor.call, Meteor.callAsync). Triggers on argument validation with check(), optimistic UI stubs, latency compensation, Meteor.Error handling, and DDPRateLimiter. Use this skill when the user asks about server-side mutation, asks about rate limiting RPC, or asks about wrapping a method with auth checks.

1시간 설치 수
1
GitHub Stars
10
업데이트
10월 14일
meteor
커뮤니티

meteor-pubsub

Use when authoring or debugging Meteor publications and subscriptions (Meteor.publish, Meteor.subscribe). Triggers on publication strategies (SERVERMERGE, NOMERGE, NOMERGENOHISTORY), the low-level publish API (added/changed/removed), cursor authorization, reactive joins, leaked documents. Use this skill when the user asks about pub/sub or asks about reactive data fetching.

1시간 설치 수
1
GitHub Stars
10
업데이트
10월 14일
meteor
커뮤니티

migrate-to-rspack

Use when migrating an existing Meteor app to Rspack (Meteor 3.4+), or upgrading Rspack 1 to 2 on Meteor 3.6 beta. Triggers on nested imports, mainModule entry points, server-only apps, replacing fourseven:scss / meteor/less / coffeescript / jorgenvatle:vite / zodern:melte with loaders, Svelte/TypeScript preprocessing or Lingui SWC plugin failures after upgrade, CommonJS default-import interop, module.exports in client graphs, Node built-ins in browser code, build / build-assets / build-chunks, .

1시간 설치 수
1
GitHub Stars
10
업데이트
10월 14일