netlify
diff --git a/‎CLAUDE.md‎
Lines changed: 136 additions & 0 deletions b/‎CLAUDE.md‎
Lines changed: 136 additions & 0 deletions
diff --git a/‎docs/commands/deploy.md‎
Lines changed: 12 additions & 65 deletions b/‎docs/commands/deploy.md‎
Lines changed: 12 additions & 65 deletions
diff --git a/‎docs/index.md‎
Lines changed: 1 addition & 1 deletion b/‎docs/index.md‎
Lines changed: 1 addition & 1 deletion
@@ -0,0 +1,136 @@
+# CLAUDE.md
+
+This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
+
+## Development Commands
+
+### Build and Development
+- `npm run build` - Compiles TypeScript using `tsc --project tsconfig.build.json`
+- `npm run dev` - Runs TypeScript compiler in watch mode
+- `npm run clean` - Removes the `dist/` directory
+
+### Testing
+- `npm test` - Runs the full test suite (unit, integration, and e2e tests)
+- `npm run test:unit` - Runs unit tests only with `vitest run tests/unit/`
+- `npm run test:integration` - Runs integration tests with `vitest run --retry=3 tests/integration/`
+- `npm run test:e2e` - Runs end-to-end tests with `vitest run --config vitest.e2e.config.ts`
+- **Single test file**: `npm exec vitest -- run tests/unit/lib/account.test.ts`
+- **Single test by name**: `npm exec vitest -- run tests/unit/lib/account.test.ts -t 'test name'`
+- **Debug tests**: `DEBUG_TESTS=true npm exec vitest -- run [test-file] -t 'test name'`
+- `npm run test:init` - Sets up test dependencies for various fixtures (Hugo, Next.js, monorepo)
+
+### Code Quality
+- `npm run lint` - Runs ESLint with cache
+- `npm run lint:fix` - Runs ESLint and automatically fixes issues
+- `npm run format` - Formats code with Prettier
+- `npm run format:check` - Checks code formatting without modifying files
+- `npm run typecheck` - Runs TypeScript type checking
+- `npm run typecheck:watch` - Runs TypeScript type checking in watch mode
+
+### Running the CLI Locally
+- `./bin/run.js [command]` - Runs the CLI locally
+- `DEBUG=true ./bin/run.js [command]` - Runs with stack traces enabled for debugging
+- `npm run start -- [command]` - Alternative way to run CLI locally
+
+## Architecture
+
+### Core Structure
+The Netlify CLI is built with **Commander.js** for CLI interface, **@netlify/js-client** for API interactions, and **TypeScript** with modular architecture. The system uses a registry pattern for managing Functions and Edge Functions, with sophisticated local development server capabilities.
+
+### Key Architectural Patterns
+
+#### Command Architecture
+- All commands extend `BaseCommand` class (`src/commands/base-command.ts`) which provides:
+  - Consistent config loading and API client setup
+  - Site information management and linking
+  - Authentication and token handling
+  - Analytics and telemetry integration
+- Commands follow a modular structure with separate `index.ts` files for exports
+- Each command supports both interactive prompts and non-interactive flag-based operation
+
+#### Registry Pattern for Runtime Management
+- **FunctionsRegistry** (`src/lib/functions/registry.ts`): Manages Netlify Functions lifecycle
+  - Supports multiple runtimes (JavaScript/TypeScript, Go, Rust)
+  - Handles hot reloading and file watching
+  - Manages function builds and serving
+- **EdgeFunctionsRegistry** (`src/lib/edge-functions/registry.ts`): Manages Edge Functions
+  - Uses `@netlify/edge-bundler` for Deno-based edge runtime
+  - Handles Edge Function deployment and local serving
+
+#### Development Server Architecture (`netlify dev`)
+The dev server (`src/commands/dev/dev.ts`) orchestrates multiple subsystems:
+- **Proxy Server**: Routes requests between static files, functions, and edge functions
+- **Functions Server**: Executes Netlify Functions locally with runtime-specific handlers
+- **Edge Functions Proxy**: Serves Edge Functions via Deno runtime
+- **Framework Detection**: Auto-detects and integrates with various web frameworks
+- **Live Tunneling**: Provides public URLs for local development via Netlify's tunnel service
+
+#### Config System
+- Uses `@netlify/config` for configuration resolution and normalization
+- Supports `netlify.toml` files with environment-specific overrides
+- Integrates with Netlify's build plugins system
+- Handles environment variable injection from multiple sources (process, .env files, Netlify site settings)
+
+### Key Libraries and Their Roles
+
+#### Core Infrastructure
+- `src/lib/api.ts` - Netlify API client wrapper with authentication
+- `src/lib/build.ts` - Build system integration and config caching
+- `src/lib/settings.ts` - Project and global settings management
+- `src/utils/command-helpers.ts` - Shared utilities for CLI commands (logging, error handling, prompts)
+
+#### Function Runtime System
+- `src/lib/functions/runtimes/` - Runtime-specific builders and executors
+  - `js/` - JavaScript/TypeScript function handling with `zip-it-and-ship-it`
+  - `go/` - Go function compilation and execution
+  - `rust/` - Rust function compilation via Cargo
+- `src/lib/functions/server.ts` - Local function server with request/response handling
+
+#### Development Tools
+- `src/utils/dev.ts` - Development server utilities and environment setup
+- `src/utils/proxy-server.ts` - HTTP proxy for routing dev server requests
+- `src/utils/detect-server-settings.ts` - Framework detection and port management
+
+#### Deployment System
+- `src/utils/deploy/` - Site deployment orchestration
+  - File hashing, diffing, and upload optimization
+  - Build artifact management and caching
+  - Progress tracking and status reporting
+
+### Testing Architecture
+- **Unit Tests** (`tests/unit/`): Test individual modules and utilities
+- **Integration Tests** (`tests/integration/`): Test full command workflows using fixtures
+- **E2E Tests**: Test complete user scenarios with real Netlify API interactions
+- **Fixtures** (`tests/integration/__fixtures__/`): Sample projects for testing different frameworks and configurations
+
+### Important Implementation Details
+
+#### Environment Variable Handling
+Environment variables are loaded from multiple sources with specific precedence:
+1. Process environment
+2. `.env` files (multiple variants supported)
+3. Netlify site settings (shared, project-specific)
+4. Addon-provided variables
+5. Build-time configuration
+
+#### Function URL Routing
+Functions are accessible via standardized URL patterns:
+- `/.netlify/functions/[function-name]` - Standard functions
+- `/.netlify/builders/[function-name]` - On-demand builders
+- Custom paths supported via function configuration
+
+#### Build Plugin Integration
+The CLI integrates with Netlify's build plugin system, allowing plugins to:
+- Modify build configuration
+- Add custom build steps
+- Integrate with the development server
+- Provide additional CLI commands
+
+### Development Setup Requirements
+- Node.js 20.12.2+ required
+- Git LFS must be installed for full test suite
+- Some integration tests require Netlify Auth Token (`NETLIFY_AUTH_TOKEN`) or login via `./bin/run.js login`
+- Live tests can be disabled with `NETLIFY_TEST_DISABLE_LIVE=true`
+
+### Coding Style:
+- Never write comments on what the code does, make the code clean and self explanatory instead
@@ -7,74 +7,18 @@ sidebar:
 # `deploy`
 
 <!-- AUTO-GENERATED-CONTENT:START (GENERATE_COMMANDS_DOCS) -->
-Create a new deploy from the contents of a folder
-Deploys from the build settings found in the netlify.toml file, or settings from the API.
+Deploy your project to Netlify
 
-The following environment variables can be used to override configuration file lookups and prompts:
+Builds and deploys your project to Netlify. Creates a draft deploy by default.
+Use --prod to deploy directly to your live site.
 
-- `NETLIFY_AUTH_TOKEN` - an access token to use when authenticating commands. Keep this value private.
-- `NETLIFY_SITE_ID` - override any linked project in the current working directory.
+The deploy command will:
+- Build your project (unless --no-build is specified)
+- Upload static files, functions, and edge functions
+- Process redirects and headers from netlify.toml or _redirects/_headers files
+- Provide deploy and function logs URLs
 
-Lambda functions in the function folder can be in the following configurations for deployment:
-
-
-Built Go binaries:
-------------------
-
-```
-functions/
-└── nameOfGoFunction
-```
-
-Build binaries of your Go language functions into the functions folder as part of your build process.
-
-
-Single file Node.js functions:
------------------------------
-
-Build dependency bundled Node.js lambda functions with tools like webpack or browserify into the function folder as part of your build process.
-
-```
-functions/
-└── nameOfBundledNodeJSFunction.js
-```
-
-Unbundled Node.js functions that have dependencies outside or inside of the functions folder:
----------------------------------------------------------------------------------------------
-
-You can ship unbundled Node.js functions with the CLI, utilizing top level project dependencies, or a nested package.json.
-If you use nested dependencies, be sure to populate the nested node_modules as part of your build process before deploying using npm or yarn.
-
-```
-project/
-├── functions
-│   ├── functionName/
-│   │   ├── functionName.js  (Note the folder and the function name need to match)
-│   │   ├── package.json
-│   │   └── node_modules/
-│   └── unbundledFunction.js
-├── package.json
-├── netlify.toml
-└── node_modules/
-```
-
-Any mix of these configurations works as well.
-
-
-Node.js function entry points
------------------------------
-
-Function entry points are determined by the file name and name of the folder they are in:
-
-```
-functions/
-├── aFolderlessFunctionEntrypoint.js
-└── functionName/
-  ├── notTheEntryPoint.js
-  └── functionName.js
-```
-
-Support for package.json's main field, and intrinsic index.js entrypoints are coming soon.
+For detailed configuration options, see the Netlify documentation.
 
 **Usage**
 
@@ -86,6 +30,7 @@ netlify deploy
 
 - `alias` (*string*) - Specifies the alias for deployment, the string at the beginning of the deploy subdomain. Useful for creating predictable deployment URLs. Avoid setting an alias string to the same value as a deployed branch. `alias` doesn’t create a branch deploy and can’t be used in conjunction with the branch subdomain feature. Maximum 37 characters.
 - `context` (*string*) - Specify a deploy context for environment variables read during the build (”production”, ”deploy-preview”, ”branch-deploy”, ”dev”) or `branch:your-branch` where `your-branch` is the name of a branch (default: dev)
+- `create-site` (*string*) - Create a new site and deploy to it. Optionally specify a name, otherwise a random name will be generated. Requires --team flag if you have multiple teams.
 - `dir` (*string*) - Specify a folder to deploy
 - `filter` (*string*) - For monorepos, specify the name of the application to run the command in
 - `functions` (*string*) - Specify a functions folder to deploy
@@ -99,6 +44,7 @@ netlify deploy
 - `prod` (*boolean*) - Deploy to production
 - `site` (*string*) - A project name or ID to deploy to
 - `skip-functions-cache` (*boolean*) - Ignore any functions created as part of a previous `build` or `deploy` commands, forcing them to be bundled again as part of the deployment
+- `team` (*string*) - Specify team slug when creating a site. Only works with --create-site flag.
 - `timeout` (*string*) - Timeout to wait for deployment to finish
 - `trigger` (*boolean*) - Trigger a new build of your project on Netlify without uploading local files
 
@@ -115,6 +61,7 @@ netlify deploy --message "A message with an $ENV_VAR"
 netlify deploy --auth $NETLIFY_AUTH_TOKEN
 netlify deploy --trigger
 netlify deploy --context deploy-preview
+netlify deploy --create-site my-new-site --team my-team # Create site and deploy
 ```
 
 
 
@@ -63,7 +63,7 @@ Provision a production ready Postgres database with a single command
 
 ### [deploy](/commands/deploy)
 
-Create a new deploy from the contents of a folder
+Deploy your project to Netlify
 
 ### [dev](/commands/dev)