Package Imports

The shadcn-templ CLI uses Go import paths for installing components and rewriting imports.

Go resolves imports through the module path in your go.mod, so there is no separate alias configuration like path mappings in other ecosystems. The CLI derives your import paths from go.mod and stores them as aliases in components.json.

Example

You configure aliases in your components.json:

{  "aliases": {    "components": "your-app/components",    "utils": "your-app/utils"  }}

Then import installed components using your module path:

import (  "your-app/components/button"  "your-app/utils")

Module Imports

In the import workflow, components are imported directly from the shadcn-templ module. No components.json and no aliases are needed:

import "github.com/axadrn/shadcn-templ/v2/components/button"

See the installation guide for the full setup of both workflows.

App

For apps that install components into their own module with the CLI.

module your-app

{  "aliases": {    "components": "your-app/components",    "utils": "your-app/utils"  }}

shadcn-templ add button

Troubleshooting

If Go cannot resolve an import after adding components, check that:

• the alias paths in components.json live under the module path of your go.mod
• you ran templ generate and go mod tidy after adding
• the component directory exists under the path the components alias points to

If a component is installed but its imports still point at the wrong module path, fix the aliases in components.json and re-run shadcn-templ add <component> --overwrite.