Herramientas locales y globales, bins y flujos de trabajo de equipo

¿Por qué usar herramientas locales?

Lo local supera a lo global

// Emulate running a tool locally vs globally
function runLocal() {
  console.log("npm run lint");
  console.log("→ uses node_modules/.bin/eslint (project version)");
}

function runGlobal() {
  console.log("eslint .");
  console.log("→ might use a different global version on each machine");
}

runLocal();
runGlobal();

Cómo aparecen las CLI

// Packages expose CLI commands via "bin" in package.json
const pkgLines = [
  "{",
  "  \"name\": \"my-tool\",",
  "  \"version\": \"1.0.0\",",
  "  \"bin\": {",
  "    \"mytool\": \"./dist/cli.js\"",
  "  }",
  "}"
];

for (const l of pkgLines) console.log(l);

// Install as devDependency => creates node_modules/.bin/mytool
console.log("After install: run with npm run or npx mytool");

PATH dentro de los scripts

// When using npm run <name>, PATH includes node_modules/.bin first
const envExplain = [
  "npm run build -> PATH starts with node_modules/.bin",
  "so running \"vite\" resolves to ./node_modules/.bin/vite"
];

for (const l of envExplain) console.log(l);

Flujo de trabajo del equipo

// Team checklist for consistent tools
const checklist = [
  "1) Add tool to devDependencies",
  "2) Add an npm script (e.g., \"lint\")",
  "3) Commit package.json and lockfile",
  "4) Teammates run: npm ci && npm run lint"
];

for (const step of checklist) console.log(step);

Globales (rara vez)

Cuestionario sobre local frente a global

Resumen