A powerful CLI toolkit for Next.js development, providing utilities for packaging, deploying, and debugging Next.js applications.
brew install wyattjoh/stable/next-dev-utilsSimply re-run the installation command from above and it'll update your installed binaries.
deno install --global --force --allow-all --name nu jsr:@wyattjoh/next-dev-utilsBefore using the CLI, you need to configure your cloud storage credentials. The tool uses S3-compatible storage for packaging and deployment.
Use the config command to manage your settings:
# Set a configuration value
nu config set <key> <value>
# Get a configuration value
nu config get <key>
# Delete a configuration value
nu config delete <key>
# List all configuration values
nu config listDeploy a test file for verification.
nu test-deploy <test-file>Arguments:
test-file(required): Path to the test file to deploy
Package and upload your Next.js application to cloud storage.
nu pack-next [options]Options:
--json: Output result as JSON--serve: Serve the package after uploading--install: Install dependencies before packing
Package and upload the current project to cloud storage.
nu pack [options]Options:
--json: Output result as JSON--serve: Serve the package after uploading--progress: Show upload progress--verbose: Enable verbose output
Debug utilities for Next.js applications.
nu debug [options]Options:
--stack: Show stack trace information-d, --directory <path>: Specify directory to debug (default: current directory)--skip-pnpm-install: Skip pnpm installation--skip-git-clean: Skip git clean operation--skip-git-bisect: Skip git bisect--skip-test: Skip test execution
Create a minimal reproduction for bug reports.
nu create-reproduction [options]Options:
--template <name>: Specify template to use--output <path>: Output directory for reproduction
Clean up stored packages from cloud storage.
nu cleanup [options]Options:
--days <number>: Delete packages older than specified days--dry-run: Preview what would be deleted without actually deleting
Execute Next.js specific commands.
nu next <command> [...args]Arguments:
command: Next.js command to execute (dev, build, start, etc.)args: Additional arguments to pass to Next.js
Manage CLI configuration.
nu config <action> [key] [value]Actions:
set <key> <value>: Set a configuration valueget <key>: Get a configuration valuedelete <key>: Delete a configuration valuelist: List all configuration values
- Cloud Storage Integration: Seamlessly upload and manage packages in S3-compatible storage
- Next.js Optimization: Specialized tools for Next.js development workflow
- Debugging Tools: Advanced debugging utilities including git bisect integration
- Reproduction Creation: Quickly create minimal reproductions for bug reports
- Configuration Management: Flexible configuration system with environment variable support
- Progress Tracking: Real-time progress indicators for long-running operations
- Deno 2.4.3 or higher
- S3-compatible storage account (AWS S3, MinIO, etc.)
- git (for debug and reproduction features)
- Next.js project (for Next.js specific commands)
# Configure your S3 credentials
nu config set S3_ENDPOINT s3.amazonaws.com
nu config set S3_BUCKET my-deployments
# Package and upload Next.js app
nu pack-next --install --json
# Deploy a specific test
nu test-deploy ./tests/integration.test.js# Run comprehensive debugging
nu debug --directory ./my-next-app
# Create a minimal reproduction
nu create-reproduction --template app-router --output ./reproduction# Clean up old packages (dry run)
nu cleanup --days 30 --dry-run
# Actually delete old packages
nu cleanup --days 30To contribute or modify the CLI:
# Clone the repository
git clone https://github.com/username/next-dev-utils.git
cd next-dev-utils
# Run in development
deno run --allow-all src/cli.ts
# Build standalone executable
deno task build
# Run tests
deno test
# Format code
deno fmt
# Lint code
deno lintMIT License - see LICENSE file for details.