- Introduced backend patterns skill with guidelines on API design, database optimization, and server-side best practices. - Added coding standards skill outlining universal coding principles for TypeScript, NestJS, and Node.js development. - Implemented continuous learning skill to automatically extract reusable patterns from Cursor sessions. - Created NestJS best practices skill detailing architecture patterns, dependency injection, error handling, and security measures. - Included various rules and templates for NestJS best practices to ensure production-ready applications.
1.6 KiB
1.6 KiB
description, disable-model-invocation
| description | disable-model-invocation |
|---|---|
| Configure your preferred package manager (npm/pnpm/yarn/bun) | true |
Package Manager Setup
Configure your preferred package manager for this project or globally.
Usage
# Detect current package manager
node scripts/setup-package-manager.js --detect
# Set global preference
node scripts/setup-package-manager.js --global pnpm
# Set project preference
node scripts/setup-package-manager.js --project bun
# List available package managers
node scripts/setup-package-manager.js --list
Detection Priority
When determining which package manager to use, the following order is checked:
- Environment variable:
CURSOR_PACKAGE_MANAGER - Project config:
.cursor/package-manager.json - package.json:
packageManagerfield - Lock file: Presence of package-lock.json, yarn.lock, pnpm-lock.yaml, or bun.lockb
- Global config:
~/.cursor/package-manager.json - Fallback: First available package manager (pnpm > bun > yarn > npm)
Configuration Files
Global Configuration
// ~/.cursor/package-manager.json
{
"packageManager": "pnpm"
}
Project Configuration
// .cursor/package-manager.json
{
"packageManager": "bun"
}
package.json
{
"packageManager": "pnpm@8.6.0"
}
Environment Variable
Set CURSOR_PACKAGE_MANAGER to override all other detection methods:
# Windows (PowerShell)
$env:CURSOR_PACKAGE_MANAGER = "pnpm"
# macOS/Linux
export CURSOR_PACKAGE_MANAGER=pnpm
Run the Detection
To see current package manager detection results, run:
node scripts/setup-package-manager.js --detect