--- schema_version: "1" id: 397b7844f2011ddf753438dec11e5b2665f379546c626d11a4863bdd3fcbf465 title: template generate project collection: developer version: current locale: en-us portal_url: https://docs.salesforce.com/developer/current/en-us/salesforcedx/sfclireference/guides/template/cli_reference_template_generate_project.md canonical_url: https://developer.salesforce.com/docs/platform/salesforce-cli-reference/guide/cli_reference_template_generate_project.html source_site: developer.salesforce.com content_type: documentation content_hash: d2585cb7acf0bc2f36fd10869fa36de29421c7f5fc7004e4e320e940d363b377 products: - Salesforce CLI Command Reference - salesforcedx --- # template generate project Generate a Salesforce DX project. ## Description for template generate project A Salesforce DX project has a specific structure and a configuration file (sfdx-project.json) that identifies the directory as a Salesforce DX project. This command generates the necessary configuration files and directories to get you started. By default, the generated sfdx-project.json file sets the sourceApiVersion property to the default API version currently used by Salesforce CLI. To specify a different version, set the apiVersion configuration variable. For example: "sf config set apiVersion=57.0 --global". ## Aliases for template generate project `force:project:create` `project:generate` ## Flags | Flag Name (Long) | Flag Name (Short) | Description | |------------------|-------------------|-------------| | ‑‑api‑version | N/A | **Type:** Value

Will set this version as sourceApiVersion in the sfdx-project.json file

Override the api version used for api requests made by this command | | ‑‑default‑package‑dir | ‑p | **Type:** Value
**Default value:** `force-app`

Default package directory name.

Metadata items such as classes and Lightning bundles are placed inside this folder. | | ‑‑flags‑dir | N/A | **Type:** Value

Import flag values from a directory. | | ‑‑json | N/A | **Type:** Boolean

Format output as json. | | ‑‑lwc‑language | N/A | **Type:** Value
**Valid Values:** `javascript`, `typescript`

Language of the Lightning Web Components. If not specified, "javascript" is used.

When set to `'typescript'`, generates TypeScript configuration files (tsconfig.json, package.json with TypeScript dependencies, and TypeScript-aware ESLint config). When you deploy the TypeScript-based Lightning Web Components, the TypeScript files are first compiled locally for validation and then the `.ts` files are deployed to your org for server-side type stripping. | | ‑‑manifest | ‑x | **Type:** Boolean

Generate a manifest (package.xml) for change-set based development.

Generates a default manifest (package.xml) for fetching Apex, Visualforce, Lightning components, and static resources. | | ‑‑name | ‑n | **Type:** Value
**Required**

Name of the generated project.

Generates a project directory with this name; any valid directory name is accepted. Also sets the "name" property in the sfdx-project.json file to this name. | | ‑‑namespace | ‑s | **Type:** Value

Namespace associated with this project and any connected scratch orgs. | | ‑‑output‑dir | ‑d | **Type:** Value
**Default value:** `.`

Directory for saving the created files.

The location can be an absolute path or relative to the current working directory. The default is the current directory. | | ‑‑template | ‑t | **Type:** Value
**Valid Values:** `standard`, `empty`, `analytics`, `reactinternalapp`, `reactexternalapp`, `angularinternalapp`, `angularexternalapp`, `agent`
**Default value:** `standard`

Template to use for project creation.

The template determines the sample configuration files and directories that this command generates. For example, the empty template provides these files and directory to get you started.



The standard template provides a complete force-app directory structure so you know where to put your source. It also provides additional files and scripts, especially useful when using Salesforce Extensions for VS Code. For example:



The analytics template provides similar files and the force-app/main/default/waveTemplates directory.

The reactinternalapp and reactexternalapp templates provide React-based project scaffolding for internal and external UI bundle use cases.

The angularinternalapp and angularexternalapp templates provide Angular-based project scaffolding for internal and external UI bundle use cases.

The agent template provides project scaffolding for building Agentforce agents and includes a sample agent called Local Info Agent. | ## Examples for template generate project Generate a project called "mywork": ```shell sf template generate project --name mywork ``` Similar to previous example, but generate the files in a directory called "myapp": ```shell sf template generate project --name mywork --default-package-dir myapp ``` Similar to prevoius example, but also generate a default package.xml manifest file: ```shell sf template generate project --name mywork --default-package-dir myapp --manifest ``` Generate a project with the minimum files and directories: ```shell sf template generate project --name mywork --template empty ``` Generate a project in which the Lightning Web Components use TypeScript rather than the default JavaScript: ```shell sf template generate project --name mywork --lwc-language typescript ```