base44 functions deploy
Deploy local function definitions to Base44.Syntax
Options
| Option | Description | Required |
|---|---|---|
[names...] | One or more function names to deploy (deploys all if omitted) | No |
--force | Delete remote functions not found locally (cannot be combined with [names...]) | No |
Authentication
Required: Yes. If not authenticated, you’ll be prompted to login first.What It Does
- Scans the
base44/functions/directory for function definitions - Discovers functions from
entry.ts/entry.jsfiles - Displays the count of functions to be deployed
- Uploads function code to Base44 sequentially
- Reports the results: deployed, unchanged, and failed counts
- If
--forceis used: also deletes remote functions that no longer exist locally
Prerequisites
- Must be run from a Base44 project directory
- Project must have function definitions in the
base44/functions/folder - Each function should be a folder with
entry.tsorentry.js
Examples
Output
--force:
Exit Codes
- Exit code 0: All functions deployed successfully (or unchanged)
- Exit code 1: One or more functions failed to deploy
Error Handling
If no functions are found in your project:--force is combined with function names:
Use Cases
- After creating new functions in your project
- When modifying existing function code
- To sync function changes before testing
- As part of your development workflow when backend logic changes
- Use
--forceto clean up remote functions that have been removed locally
Notes
- This command deploys function code
- Changes are applied to your Base44 project immediately
- Deploy results per function:
deployed,unchanged, orerror --forcecannot be combined with specific function names- Make sure to test functions in a development environment first
- Function definitions are located in the
base44/functions/directory - Use
entry.tsorentry.jsfor functions - For how to create functions, see functions-create.md

