chore: update documentation to replace npm with pnpm for installation and command execution

Author: muniter

CLAUDE.md

@@ -9,14 +9,14 @@ This is `@muniter/queue`, a TypeScript queue system inspired by Yii2-Queue archi
 ## Essential Commands
 
 ### Development Commands
-- `npm run build` - Build TypeScript to JavaScript
-- `npm run dev` - Watch mode for development (TypeScript compiler)
-- `npm run lint` - Type checking with TypeScript compiler
-- `npm test` - Run all tests with Vitest
+- `pnpm run build` - Build TypeScript to JavaScript
+- `pnpm run dev` - Watch mode for development (TypeScript compiler)
+- `pnpm run lint` - Type checking with TypeScript compiler
+- `pnpm test` - Run all tests with Vitest
 
 ### Worker Commands
-- `npm run queue:worker` - Start a queue worker
-- `npm run queue:worker:isolate` - Start worker with job isolation
+- `pnpm run queue:worker` - Start a queue worker
+- `pnpm run queue:worker:isolate` - Start worker with job isolation
 
 ### CLI Worker Options
 The CLI worker supports these arguments:

README.md

@@ -13,12 +13,12 @@ A TypeScript queue system inspired by Yii2-Queue architecture, providing a clean
 ## Installation
 
 ```bash
-npm install @muniter/queue
+pnpm add @muniter/queue
 ```
 
 For SQS support:
 ```bash
-npm install @muniter/queue @aws-sdk/client-sqs
+pnpm add @muniter/queue @aws-sdk/client-sqs
 ```
 
 ## Quick Start
@@ -289,19 +289,19 @@ export class YourDatabaseAdapter implements DatabaseAdapter {
 
 ```bash
 # Database driver (requires your adapter)
-npm run queue:worker -- --driver db
+pnpm run queue:worker -- --driver db
 
 # SQS driver  
-npm run queue:worker -- --driver sqs --queue-url https://sqs.us-east-1.amazonaws.com/123/test
+pnpm run queue:worker -- --driver sqs --queue-url https://sqs.us-east-1.amazonaws.com/123/test
 
 # File driver
-npm run queue:worker -- --driver file --path ./queue-data
+pnpm run queue:worker -- --driver file --path ./queue-data
 
 # Run once and exit
-npm run queue:worker -- --no-repeat
+pnpm run queue:worker -- --no-repeat
 
 # Custom polling timeout
-npm run queue:worker -- --timeout 10
+pnpm run queue:worker -- --timeout 10
 ```
 
 ## API Reference
@@ -337,17 +337,17 @@ interface JobMap {
 Run the test suite:
 
 ```bash
-npm test
+pnpm test
 ```
 
 Build the project:
 ```bash
-npm run build
+pnpm run build
 ```
 
 Type checking:
 ```bash
-npm run lint
+pnpm run lint
 ```
 
 ## Architecture

example-queue-project/README.md

@@ -25,12 +25,12 @@ This example shows the **separation of concerns** pattern recommended for produc
 
 1. Install dependencies:
 ```bash
-npm install
+pnpm install
 ```
 
 2. Build the project:
 ```bash
-npm run build
+pnpm run build
 ```
 
 ## Usage
@@ -40,7 +40,7 @@ npm run build
 In one terminal, start the background workers that will process jobs:
 
 ```bash
-npm run process-jobs
+pnpm run process-jobs
 ```
 
 This will:
@@ -54,7 +54,7 @@ This will:
 In another terminal, add jobs to be processed:
 
 ```bash
-npm run add-job
+pnpm run add-job
 ```
 
 This will add various types of jobs:
@@ -98,8 +98,8 @@ In a real production environment, you would:
 
 ## Try It
 
-1. Start workers: `npm run process-jobs`
-2. In another terminal: `npm run add-job`
+1. Start workers: `pnpm run process-jobs`
+2. In another terminal: `pnpm run add-job`
 3. Watch the jobs get processed in real-time!
 4. Try adding jobs multiple times to see concurrent processing
 5. Stop workers with Ctrl+C

src/drivers/redis.ts

@@ -20,7 +20,7 @@ interface RedisOperations {
   exists(...keys: string[]): Promise<number>;
 }
 
-// Type for the redis npm package client (simplified - we'll use duck typing)
+// Type for the redis package client (simplified - we'll use duck typing)
 export interface RedisClient {
   [key: string]: any; // Allow any redis client that has the methods we need
 }