CodeVetter · Repo Unpack · Contributor handoff
meteor/meteor
Start by identifying whether a change belongs to the CLI/build tool, an application runtime package, an npm integration, or documentation tooling. Tests and CI were inspected, not executed, and this bounded brief cannot establish whole-repository coverage or absence of defects. Future execution should use the repository's existing checks only when authorized and preserve architecture, package, and runtime boundaries.
- Read AGENTS.md and DEVELOPMENT.md first: the former identifies CLI/build/package entrypoints, and the latter explains checkout-specific behavior and recursive submodule requirements.
- For CLI behavior, follow command registration and the relevant ProjectContext stages; command callbacks should return appropriate results rather than call process.exit directly.
- For build changes, read Isobuild terminology and preserve watch-set collection; incremental runs retain cached server watch sets and previous builders.
- Choose the existing test layer by scope: root scripts expose Jest unit/E2E/native checks, while AGENTS.md distinguishes CLI self-tests from package tests and recommends test-in-console for terminal package results.
- Treat test definitions as intended checks, not results: the unit script uses --passWithNoTests, excludes package tests, and accounts provider scenarios deliberately exercise stubbed service data.
- Formatting and linting use oxfmt/oxlint with explicit ignore files and package allowlists; the formatter specifies two spaces, double quotes, semicolons, and a 100-character width, so a root check does not cover every source file.
- Before changing bundled Node/npm/MongoDB/TypeScript components, inspect the dev-bundle requirements; DEVELOPMENT.md requires version consideration and describes publication as a Meteor staff infrastructure step.
- Preserve platform/process edge cases: Rspack bypasses npx on Windows when arguments contain whitespace, detaches POSIX processes for group cleanup, and runAll preserves test buildMode while separately setting NODE_ENV.