lookup-npm-dependencies-version

pa-y-kunimoto's avatarfrom pa-y-kunimoto

Look up the latest stable versions of NPM packages using npm view command. Use when planning a project, updating dependencies, or when the user asks about current package versions for Node.js/TypeScript projects.

⭐0stars🔀0forks📁View on GitHub🕐Updated Jan 9, 2026

When & Why to Use This Skill

This Claude skill enables real-time lookup of NPM package versions and metadata using the `npm view` command. It helps developers maintain up-to-date dependencies, check for deprecations, and ensure compatibility across Node.js and TypeScript projects by providing accurate, stable version data and ready-to-use installation commands, effectively bridging the gap between AI knowledge cutoffs and the current state of the NPM registry.

Use Cases

  • Project Planning & Initialization: Determining the latest stable versions of a specific technology stack (e.g., Express, React, Zod) when starting a new project to ensure a modern and secure foundation.
  • Dependency Maintenance: Quickly checking for newer versions of existing packages to keep the codebase performant and up-to-date with the latest security patches.
  • Compatibility & Peer Dependency Checks: Verifying peer dependency requirements and Node.js engine constraints before installation to prevent environment conflicts and build failures.
  • Package Auditing & Troubleshooting: Identifying deprecated packages and exploring available distribution tags (such as beta, next, or legacy versions) to assist in debugging or experimental development.
namelookup-npm-dependencies-version
descriptionLook up the latest stable versions of NPM packages using npm view command. Use when planning a project, updating dependencies, or when the user asks about current package versions for Node.js/TypeScript projects.
allowed-toolsBash(npm view:*)

NPM Dependencies Version Lookup

Look up the latest stable versions of NPM packages using npm view command to get accurate, real-time version information.

Instructions

  1. Identify packages to look up:

    • Use packages specified by the user
    • Or check the current feature's plan.md for technology stack and dependencies
  2. Run npm view for each package:

    npm view <package-name> version
    
    • For multiple packages, run commands in parallel:
    npm view express version
    npm view mysql2 version
    npm view typescript version
    
    • To see more details (description, dependencies, etc.):
    npm view <package-name>
    
  3. Check peer dependencies if needed:

    npm view <package-name> peerDependencies
    
  4. Generate version report as a markdown table:

    ## NPM Dependencies Version Report
    
    **Generated**: [DATE]
    
    ### Runtime Dependencies
    
    | Package | Latest Version |
    |---------|----------------|
    | express | 5.0.1 |
    | mysql2 | 3.11.0 |
    
    ### Development Dependencies
    
    | Package | Latest Version |
    |---------|----------------|
    | typescript | 5.7.2 |
    | vitest | 2.1.8 |
    
  5. Provide installation command:

    # Runtime dependencies
    aikido-npm install express@^5.0.1 mysql2@^3.11.0
    
    # Development dependencies
    aikido-npm install -D typescript@^5.7.2 vitest@^2.1.8
    

Useful npm view Commands

Command Description
npm view <pkg> version Latest stable version
npm view <pkg> versions All available versions
npm view <pkg> dist-tags Tagged versions (latest, next, beta)
npm view <pkg> peerDependencies Peer dependency requirements
npm view <pkg> engines Node.js version requirements
npm view <pkg> deprecated Check if deprecated

Version Notation

Notation Usage Example
^ (caret) Most packages - allows minor/patch updates ^1.2.3
~ (tilde) Packages with frequent breaking changes ~1.2.3
Exact Critical dependencies requiring stability 1.2.3

Example Workflow

# 1. Check latest versions
npm view express version        # => 5.0.1
npm view mysql2 version         # => 3.11.0
npm view zod version            # => 3.24.1
npm view typescript version     # => 5.7.2
npm view vitest version         # => 2.1.8

# 2. Check Node.js requirements
npm view express engines
npm view mysql2 engines

# 3. Install with specific versions
aikido-npm install express@^5.0.1 mysql2@^3.11.0 zod@^3.24.1
aikido-npm install -D typescript@^5.7.2 vitest@^2.1.8