Template Commands
Esta página aún no está disponible en tu idioma.
Use these template commands to configure and extend projects created with bun create metaideas/init <name>.
Commands
bun template setup
Configure a newly created project. This command does the following:
- It prompts you to select the application and package workspaces to keep.
- It sets the project name, which is also the package scope.
- It rewrites
@init/references with the project name. - It records the source template, commit, and creation time in
.template.json. - It removes content that only template maintainers use, including the marked template sections of
AGENTS.md.
bun template setupbun template rename
Rename the project. Rewrite its package scope references.
bun template rename --name <name> [--scope <scope>]bun template add app <name>
Copy an application workspace from the template with Turbo generators. Apply the package scope of the project.
bun template add app webbun template add package <name>
Copy a package workspace from the template with Turbo generators. Apply the package scope of the project.
bun template add package authProject scripts
bun run scripts is the extensible entry point for scripts that the project owns.
Updating Your Project
bun template setup creates .template.json. The file contains the template repository, the commit used to create the project, and the creation time:
{ "template": "metaideas/init", "commit": "<sha>", "createdAt": "<ISO date>" }There is no automated template update or check command. To add template improvements, ask the coding agent to compare metaideas/init from the recorded commit to HEAD. Ask it to apply changes that are relevant to the project. Before it compares the code, tell it to propagate upstream deletions. Tell it to normalize the renamed scope. Local @<scope>/ references correspond to upstream @init/ references.