Use pnpm instead of npm in check-data-files.mjs

[IEvangelist]

Summary

Fixes #872

The repository is configured as a pnpm workspace (pnpm-workspace.yaml, pnpm-lock.yaml, "packageManager": "pnpm@10.30.1"), but src/frontend/scripts/check-data-files.mjs hardcoded:

execSync('npm run update:all', { stdio: 'inherit' });

When pnpm dev is run and missing data files are detected, the script jumps out of the active pnpm environment and forces npm run update:all. Running npm inside a pnpm workspace:

• Ignores pnpm-lock.yaml
• Creates an unnecessary package-lock.json
• Generates an incompatible flat node_modules structure
• Can corrupt or destabilize the local development environment
• Breaks workspace dependency consistency

Change

This repo is intended to strictly use pnpm (it ships a pnpm-workspace.yaml and pins packageManager to pnpm@10.30.1), so the script now invokes pnpm directly:

execSync('pnpm run update:all', { stdio: 'inherit' });

This keeps the call site simple and matches every other script invocation in src/frontend/package.json (dev, start, build, lint, test, update:all, etc. all use pnpm).

[Copilot]

Pull request overview

Updates the frontend “missing data files” safety check to keep all script execution inside the repo’s pnpm workspace, avoiding npm lockfile/node_modules side effects.

Changes:

• Switch check-data-files.mjs to run pnpm run update:all instead of npm run update:all.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.