nodejs-package-json

shaowei-g's avatarfrom shaowei-g

Patch a Node.js project's package.json for standard build automation. Use when asked to add/standardize package.json scripts like prebuild/postbuild for TypeScript builds (rimraf dist + tsc-alias), adjust prebuild for Next.js (rimraf dist .next), or ensure an existing package.json pkg config includes required scripts/assets/targets/outputPath.

⭐0stars🔀0forks📁View on GitHub🕐Updated Dec 31, 2025
[Developer Tools]

When & Why to Use This Skill

This Claude skill automates the standardization of Node.js build processes by patching `package.json` files. It ensures projects follow best practices for build automation, specifically handling TypeScript path aliasing, Next.js build cleanup, and executable packaging configurations to reduce manual setup errors and improve CI/CD reliability.

Use Cases

  • Standardizing Build Pipelines: Automatically adding prebuild and postbuild scripts to ensure a clean build environment using rimraf and tsc-alias.
  • Next.js Project Optimization: Configuring specialized cleanup scripts that target both the 'dist' and '.next' directories to prevent stale build artifacts.
  • Binary Distribution Setup: Validating and patching the 'pkg' configuration object to ensure all necessary assets, targets, and output paths are correctly defined for standalone executable generation.
  • TypeScript Path Resolution: Streamlining the integration of tsc-alias into the build workflow to resolve module aliases in compiled output, preventing runtime import errors.
namenodejs-package-json
descriptionPatch a Node.js project's package.json for standard build automation. Use when asked to add/standardize package.json scripts like prebuild/postbuild for TypeScript builds (rimraf dist + tsc-alias), adjust prebuild for Next.js (rimraf dist .next), or ensure an existing package.json pkg config includes required scripts/assets/targets/outputPath.

Node.js package.json

Goal

Quickly and safely update package.json to include:

  • scripts.prebuild: rimraf dist (or rimraf dist .next for Next.js)
  • scripts.postbuild: tsc-alias
  • If pkg config exists: ensure scripts/assets/targets/outputPath contain required entries

Workflow

  1. Run the patcher (auto-detects Next.js):

    • python3 "${CODEX_HOME:-$HOME/.codex}/skills/nodejs-package-json/scripts/patch_package_json.py" --path package.json

  2. If Next.js auto-detection is wrong, force it:

    • Force Next.js: --nextjs true
    • Force non-Next.js: --nextjs false

  3. If prebuild or postbuild already exist with different values:

    • Re-run with --force to overwrite to the recommended defaults.

Notes

  • This skill edits package.json only; it does not install dependencies. Ensure rimraf and tsc-alias are available (typically as devDependencies).
  • The patcher only edits pkg settings if a top-level pkg object already exists (it does not add one).