Migrate from Yarn to pnpm package manager with latest best practices

Migrate Discord Bot Project from Yarn to pnpm

Objective

Migrate the entire project from Yarn package manager to pnpm, implementing the latest pnpm version and best practices for optimal performance, security, and development experience.

Scope of Migration

1. Package Manager Configuration

• Update package.json to use latest pnpm package manager field
• Replace yarn.lock with pnpm-lock.yaml
• Update all npm scripts to use pnpm commands instead of yarn
• Ensure compatibility with Node.js >= 20.0.0 requirement

2. Docker Configuration Updates

• Update Dockerfile to use pnpm instead of yarn
• Optimize Docker build stages for pnpm's efficient node_modules structure
• Update dependency installation commands and caching strategies
• Maintain security best practices in Docker configuration

3. CI/CD Pipeline Updates

• Update all GitHub Actions workflows (test.yml, build.yml, etc.) to use pnpm
• Update caching strategies in workflows to use pnpm cache
• Update file path triggers to include pnpm-lock.yaml instead of yarn.lock
• Ensure all workflow steps use pnpm commands

4. Development Scripts & Commands

• Update all npm scripts in package.json to use pnpm syntax
• Update build, start, dev, test, and deployment commands
• Update Docker-related scripts to use pnpm
• Maintain compatibility with existing development workflow

5. Documentation & Configuration

• Update README.md with pnpm installation and usage instructions
• Update CONTRIBUTING.md with pnpm development guidelines
• Add .npmrc configuration file with pnpm best practices
• Update any shell scripts that reference yarn

Technical Requirements

pnpm Best Practices to Implement

1. Latest pnpm version: Use pnpm 9.x (latest stable)
2. Workspace configuration: If applicable, configure workspaces properly
3. Node modules structure: Leverage pnpm's efficient symlink-based node_modules
4. Security: Configure pnpm for security best practices
5. Performance: Utilize pnpm's faster installation and better disk usage
6. Lock file: Ensure pnpm-lock.yaml is properly generated and committed

Configuration Files to Create/Update

• .npmrc with pnpm-specific configurations
• Update packageManager field in package.json to latest pnpm version
• Configure pnpm settings for security and performance

CI/CD Considerations

• Use pnpm/action-setup in GitHub Actions for proper pnpm setup
• Update caching strategies to leverage pnpm's store
• Maintain build performance and security scanning capabilities

Current Project Context

• Framework: Discord.js bot with TypeScript
• Current Package Manager: Yarn 1.22.22
• Node Version: >= 20.0.0
• Build Tools: TypeScript, ESLint, Vitest
• Docker: Multi-stage build with Alpine Linux
• Dependencies: Discord.js, Express, Redis, PostgreSQL drivers

Migration Strategy

1. Phase 1: Update package.json and create pnpm configuration
2. Phase 2: Generate pnpm-lock.yaml and remove yarn.lock
3. Phase 3: Update Docker configuration for pnpm
4. Phase 4: Update all GitHub Actions workflows
5. Phase 5: Update documentation and scripts
6. Phase 6: Test all functionality to ensure compatibility

Success Criteria

• All dependencies install correctly with pnpm
• All npm scripts work with pnpm commands
• Docker build succeeds with pnpm
• CI/CD pipelines pass with pnpm
• Application runs correctly in development and production
• Faster installation times compared to yarn
• Maintained security and dependency management standards

Notes

• Maintain backward compatibility where possible
• Follow the existing code style and project structure
• Ensure all security configurations are preserved
• Test thoroughly before finalizing the migration
• Document any breaking changes or new requirements

This migration will modernize the project's package management while maintaining all existing functionality and improving development experience through pnpm's advanced features.