tooling/use-project-scripts

Dlaczego

The project's scripts pin the tool versions, flags and config the team agreed on. Running npx eslint with another version, installing a global tool, or running npm install in a pnpm project rewrites the lockfile, produces different results and creates noise in the pull request.

Poprawka

Detect the package manager from the lockfile (package-lock.json npm, pnpm-lock.yaml pnpm, yarn.lock Yarn, bun.lock Bun) or the packageManager field, then run <pm> run lint, test, typecheck, build as defined in package.json. If a script is missing, propose adding it rather than running an ad-hoc command.

Przykłady

# bad: in a pnpm project
npm install && npx eslint .
# good
pnpm install --frozen-lockfile && pnpm run lint

Źródła

• npm CLI documentation, scripts
• Node.js, Corepack (packageManager field)

Przeczytaj w terminalu

npx github:dawidolko/frontend-skills explain tooling/use-project-scripts