Skip to content
Landix UIGet All Access
Documentation menu / Installation

Installation

Install free and licensed Landix UI components into a shadcn/ui project with the shadcn CLI.

From section to your own website

Landix UI delivers editable sections through its registry. You do not need to run this documentation site, create a database, or configure Gumroad to use a free or purchased block.

Install the two free sections

Hero 01 and Pricing 01 are free source downloads. No account, Gumroad key, or license header is needed. These direct registry URLs do not use the paid @landix alias or call license verification.

Prerequisites: Node.js 20.9+ and npm, a Next.js App Router project with TypeScript, Tailwind CSS 4, and the @/ import alias. Use Terminal on macOS/Linux or PowerShell on Windows. Check node --version and npm --version first.

Terminal or PowerShell: any folder
node --version
npm --version

For a new project:

Terminal — your project folder
npx create-next-app@16.2.10 my-landix-site --ts --tailwind --eslint --app --src-dir --import-alias "@/*" --use-npm
cd my-landix-site
npx shadcn@latest init

For an existing project, open its folder and run shadcn init only if components.json is missing. Commit or back up your work first. Review CLI prompts; do not overwrite customized files without checking the diff.

Terminal — your project folder
npx shadcn@latest add https://landix.design/api/registry/hero-01
npx shadcn@latest add https://landix.design/api/registry/pricing-01

Success: shadcn reports the added files under components/landix. If the registry is unreachable, stop and fix the reported error before retrying. These free downloads remain available even if a missing or invalid paid-block license is configured in your project.

File contents: src/app/page.tsx
import Hero from "@/components/landix/hero-01/preview";
import PricingPreview from "@/components/landix/pricing-01/preview";

export default function Page() {
  return <><Hero /><PricingPreview /></>;
}

Run npm run dev and open the local address printed in the terminal. Replace the sample text, prices, and links. These are interface sections, not booking, payment, or subscription services. Run npm run build before deployment.

Remaining sections need Lifetime access. Continue below only when installing a paid block.

1. Purchase your license

Purchase Lifetime Access on Gumroad and copy the license key from your receipt. Keep it private.

Install Node.js 20.9 or newer with npm and a code editor. Open Terminal on macOS/Linux or PowerShell on Windows and check:

Terminal or PowerShell - any folder
node --version
npm --version

For a new website, run these commands from your projects folder:

Terminal — your project folder
npx create-next-app@16.2.10 my-landix-site --ts --tailwind --eslint --app --src-dir --import-alias "@/*" --use-npm
cd my-landix-site
npx shadcn@latest init

Accept the setup prompts. For an existing Next.js project, open its folder and run shadcn init only if components.json is missing. Landix UI uses App Router, TypeScript, Tailwind CSS 4 and the @/ alias.

2. Enter your key in shadcn config

Open components.json in your website folder. Add this @landix entry inside registries, keeping the existing settings and other registries. shadcn supports ${LANDIX_LICENSE_KEY} references in registry headers and resolves them from the environment running the CLI:

Merge into components.json
{
  "registries": {
    "@landix": {
      "url": "https://landix.design/api/registry/{name}",
      "headers": {
        "x-landix-license": "${LANDIX_LICENSE_KEY}"
      }
    }
  }
}

Keep the key out of source control and shared logs; the ${LANDIX_LICENSE_KEY} reference itself is safe to commit. The CLI sends the resolved value in the request header.

No browser activation or account session is needed. Your key is verified with Gumroad when you add a component.

From the folder containing components.json and package.json, securely enter the key in PowerShell, then use the shadcn CLI with the @landix name. The key is not echoed or saved in command history:

PowerShell: from your website folder
npx shadcn@latest add @landix/hero-02

Free blocks do not need the license header and can be installed with the direct commands in the previous section. For paid blocks, choose a component in the documentation and use its namespaced @landix install command so shadcn applies the configured header; a direct registry URL does not automatically use named-registry headers. shadcn adds the source, styles, assets and dependencies to your project.

Open src/app/page.tsx and render the installed block:

File contents - src/app/page.tsx
import HeroPreview from "@/components/landix/hero-02/preview";

export default function Page() {
  return <HeroPreview />;
}

Edit the installed files to customize your website. Your deployed website does not need the license key; it is used only by the CLI.

3. Run your website

Terminal — your project folder
npm run dev

Wait for Ready, then open http://localhost:3000. You should see your hero. Edit text and save to see it update. Keep the terminal running; Ctrl+C stops the server.

If port 3000 is busy, use port 3001 and open the address printed in the terminal:

Terminal — your project folder
npm run dev -- --port 3001

4. Build or deploy

Stop the development server with Ctrl+C. From the same project folder:

Terminal — your project folder
npm run build
npm start

A successful build lists the routes. npm start serves that production build locally. To publish your own website, push it to a private repository and import it into a Next.js-compatible host. Use npm run build as the build command. Configure your domain and service credentials with the host.

Troubleshooting

Node or npm is not recognized

Install Node.js 20.9+ with npm, then reopen the terminal. On managed computers, ask your administrator.

No package.json / ENOENT

Open the folder containing package.json in your terminal, then retry.

401 or 403 from the registry

Check the @landix header in components.json, set LANDIX_LICENSE_KEY in the PowerShell session, use the namespaced CLI command, and confirm the current Lifetime license is not refunded or under an unresolved dispute. Never share the key in logs or support messages.

Verification temporarily unavailable (503)

The registry could not complete verification or its server configuration is unavailable. Wait briefly and retry the CLI command. If it persists, contact Landix UI support with the response request ID, if shown, and do not include your license key.

Permission or network error during npm install

Use a writable folder and check npm registry access. Save the error instead of running unknown repair commands as administrator.

Get help

For purchase/key problems, contact the seller through your Gumroad receipt. For code issues, open an issue in the landix-art/landix-ui GitHub repository. Include the command, error, operating system and Node version. Remove license keys, email addresses and .env secrets before sharing logs.