OpenParable
Skip to content
← Back to skills

Update NPM Packages

Development
update-npm-packages

Update NPM Packages is an Agent Skill for development published in the PowerShell/vscode-powershell repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Guide for updating NPM dependencies in vscode-powershell. Use when asked to update packages, fix vulnerabilities, or bump dependency versions.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/PowerShell/vscode-powershell/blob/HEAD/.github/skills/update-npm-packages/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/update-npm-packages, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

Updating NPM Packages

Read docs/development.md "Tracking Upstream Dependencies" section for full context.

Rules

  • Dependencies are split into three groups:
    • dependencies — runtime packages bundled into the extension
    • devDependencies — build tools only (minimum for Azure DevOps pipeline)
    • optionalDependencies — lint, type-checking, and test tools (for development and GitHub Actions)
  • Always use npm install --include=optional to get all three groups.
  • The .npmrc uses an Azure Artifacts mirror; read its comments for authentication instructions.
  • When updating engines.vscode follow the "Tracking Upstream Dependencies" section of docs/development.md.
  • Update the ESLint packages (eslint, @eslint/js, typescript-eslint, eslint-config-prettier) together and fix any new lint warnings.
  • After updating, verify: npm run compile, npm run lint, npm audit.
  • For vulnerabilities in transitive dependencies identified by npm audit, add an overrides entry in package.json rather than using npm audit fix --force which may downgrade our packages.
  • Check that each overrides entry is still necessary.