From npm-package-updates
Guides through npm package updates including minor/patch updates and major version updates. Use when user wants to update npm dependencies, handle breaking changes, manage package versions, or run npm outdated/update commands.
npx claudepluginhub forumone/f1-genai-starter --plugin npm-package-updatesThis skill uses the workspace's default tool permissions.
This skill guides you through the process of updating npm packages in this project, including minor/patch updates and major version updates.
Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.
Guides building MCP servers enabling LLMs to interact with external services via tools. Covers best practices, TypeScript/Node (MCP SDK), Python (FastMCP).
Generates original PNG/PDF visual art via design philosophy manifestos for posters, graphics, and static designs on user request.
This skill guides you through the process of updating npm packages in this project, including minor/patch updates and major version updates.
Determine if ddev is running:
ddev describe 2>/dev/null
ddev gesso. Example: npm update --save becomes ddev gesso npm update --savenvm use to ensure the correct Node versionRun npm ci to ensure installed packages match package-lock.json
Minor and patch updates follow semantic versioning and should not introduce breaking changes.
Update packages:
npm update --save
This updates packages to their latest minor and patch versions within the semver range specified in package.json.
Fix any issues:
Test the updates: Run all three test suites to ensure everything still works:
npm run build # Build application or theme
npm run test # Run linting and TypeScript checks
npm run build-storybook # Build Storybook
Commit the changes:
git add package.json package-lock.json [other modified files]
git commit -m "Minor and patch version updates"
Major version updates may introduce breaking changes and require careful review.
Identify packages with major updates:
npm outdated
Look for packages where the "Latest" version has a different major version than "Current".
Prioritize and filter updates:
Research and summarize ALL major updates:
For each package with a major update available:
a. Research breaking changes:
b. Check impact on codebase:
c. Document findings: Create a summary for each package including:
Present summary to user and await decision:
For each approved major update: c. Update the package:
# For dev dependencies
npm install <package-name>@latest --save-dev
# For production dependencies
npm install <package-name>@latest --save
d. Test the update: Run the full test suite:
npm run build
npm run test
npm run build-storybook
d. Handle failures:
e. Commit the update:
git add package.json package-lock.json [other modified files]
git commit -m "Update <package-name> to v<version>"
All updates must pass these tests before committing:
Next.js Build (npm run build)
Test Suite (npm run test)
Storybook Build (npm run build-storybook)
"Minor and patch version updates""Update <package-name> to v<version>"For updating @inquirer/prompts from v7 to v8:
lib/create-component.mjsnpm install @inquirer/prompts@latest --save-dev"Update @inquirer/prompts to v8.0.1"