Skip to main content

Installation

Prerequisites, setup, running, and building the AI & SaaS Landing Page Bundle locally.

Table of Contents

Prerequisites

Before installing, make sure you have:

  • Node.js 18.17.0 or later
  • pnpm 9.0.0 or later
  • A terminal (macOS/Linux shell, or Windows PowerShell / Git Bash)

Warning

This project must be installed with pnpm. Installing with npm install or yarn install will not correctly set up the project, and it will fail to run.

Node Version

Check your installed Node version:

node -v

You need v18.17.0 or higher. If you're on an older version, install a current LTS release from nodejs.org or via a version manager such as nvm:

nvm install --lts
nvm use --lts

Installing pnpm

If you don't already have pnpm installed:

npm install -g pnpm@9

Verify the install:

pnpm -v

Extracting the Project

  1. Unzip the downloaded archive to a folder of your choice.
  2. Open a terminal in that folder.

The download includes all three template variants, ready to install and run.

Installing Dependencies

From the root folder of the extracted project (not from inside one of the individual template folders):

pnpm install

This single command installs everything needed to run all three templates.

Note

Always run installation and start-up commands from the project's root folder.

Running All Templates

Start all 3 variants at once in development mode:

pnpm dev
TemplateURL
V1 — SaaS (Launchpad)http://localhost:3000
V2 — AI Tool (Lumina)http://localhost:3001
V3 — Dev Tool (Forge)http://localhost:3002

[Screenshot: Terminal output showing all three dev servers starting]

Running an Individual Template

To run only one variant at a time:

pnpm dev:saas       # V1 — http://localhost:3000
pnpm dev:ai-tool    # V2 — http://localhost:3001
pnpm dev:devtool    # V3 — http://localhost:3002

Build Commands

Build all 3 templates for production:

pnpm build

To build a single template only:

pnpm build:saas
pnpm build:ai-tool
pnpm build:devtool

Note

For actual production hosting, deploy to Vercel rather than running the project locally — see the Deployment guide. Running a local production build is mainly useful for previewing your changes before deploying.

Common Installation Issues

"Cannot find module" or similar errors after installing

Caused by installing with npm or yarn instead of pnpm, or by running the install command from inside one of the individual template folders instead of the project root. Fix: delete any node_modules folders that were created, then run pnpm install again from the root folder.

Peer dependency warnings during install

A small number of peer dependency warnings may appear during installation — these are expected and don't affect the project. You shouldn't need to change anything unless you manually change one of the pinned package versions.

Troubleshooting

pnpm dev starts but a page 404s or shows a blank screen

Confirm you're visiting the correct port for the variant you intend to view (3000 / 3001 / 3002 — see Running All Templates). Each variant is a separate site with its own server.

Changes I make don't show up in the browser

Make sure the development server is still running in your terminal, and try a hard refresh in your browser. If you edited a configuration file rather than page content, restart the development server — configuration changes require a restart to take effect.

If you hit an issue not covered here, check the FAQ or reach out through the support channels in Getting Started.

Previous

Getting Started

Next

V1 — Launchpad (SaaS)