Command-line interface tool for initializing, developing, and maintaining NestJS applications
—
Pending
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Pending
The risk profile of this skill
Display comprehensive information about your NestJS project including dependencies, versions, system information, and project configuration. The info command provides a detailed overview of your development environment and project setup.
Displays detailed project and system information in a formatted, easy-to-read layout.
# Display project information
nest info [options]
nest i [options]
# Options:
-h, --help # Output usage informationUsage Examples:
# Display full project information
nest info
# Using alias
nest i
# Get help for info command
nest info --helpThe command displays comprehensive system details:
# System Information Output:
[System Information]
OS Version : Linux 5.4.0
NodeJS Version : v18.17.0
YARN Version : 1.22.19
NPM Version : 9.8.1
[Nest CLI]
Nest CLI Version : 10.1.0
[Nest Platform Information]
platform-express version : 10.1.0
platform-fastify version : Not Found
platform-socket.io version : Not Found
platform-ws version : Not FoundInformation about installed NestJS packages and their versions:
# NestJS Package Versions:
@nestjs/core version : 10.1.0
@nestjs/common version : 10.1.0
@nestjs/microservices version: 10.1.0
@nestjs/websockets version : 10.1.0
@nestjs/testing version : 10.1.0
@nestjs/platform-express version: 10.1.0
@nestjs/cli version : 10.1.0
@nestjs/schematics version : 10.0.2Information about key development tools and their versions:
# Development Tools:
TypeScript version : 5.1.6
Webpack version : 5.88.0
Jest version : 29.6.0
Prettier version : 3.0.0
ESLint version : 8.44.0Details about the current project setup:
# Project Configuration:
Nest CLI Configuration:
Source Root: src
Collection: @nestjs/schematics
Entry File: mainThe command uses a clean, organized format with:
Some information is displayed in table format for better organization:
┌─────────────────────────┬─────────────────────────┐
│ Package │ Version │
├─────────────────────────┼─────────────────────────┤
│ @nestjs/core │ ^10.1.0 │
│ @nestjs/common │ ^10.1.0 │
│ @nestjs/platform-express│ ^10.1.0 │
└─────────────────────────┴─────────────────────────┘Quickly verify your development environment setup:
# Check if all required tools are installed
nest info
# Verify specific version requirements
# Useful before starting development or deploymentGather system information for bug reports and support:
# Collect information for GitHub issues
nest info > system-info.txt
# Share environment details with team members
# Useful for debugging environment-specific issuesAudit project dependencies and versions:
# Check for outdated packages
nest info
# Verify consistent versions across environments
# Useful during project maintenanceThe command automatically detects:
When dependencies are not found:
# Example output for missing packages:
@nestjs/graphql version : Not Found
@nestjs/typeorm version : Not Found
Webpack version : Not FoundFor monorepo projects, the command shows:
The command reads and displays information from:
package.json - for dependency versionsnest-cli.json - for CLI configurationtsconfig.json - for TypeScript settingsangular.json - for workspace configuration (if present)# In CI/CD pipelines
nest info
# Use exit code to verify required tools are present
# Include in deployment scripts for environment validation# Check version consistency across environments
nest info | grep "@nestjs/core"
# Useful for ensuring production matches development versionsThe command respects environment variables:
NODE_ENV - affects some package detectionNPM_CONFIG_PREFIX - for global package locationsWhile not built-in, you can process the output for programmatic use:
# Parse specific information
nest info | grep "NodeJS Version" | cut -d: -f2
nest info | grep "@nestjs/core" | cut -d: -f2The command helps identify:
Diagnose environment issues: