solidjs /solid-start

SolidStart, the Solid app framework

★ 5,922⑂ 423👁 45⑃ 1,093● 1,019▤ 63
TypeScriptMITCreated 2021-03-30docs.solidjs.com/solid-start/v2/
More from this author
Download: @solidjs/[email protected]@solidjs/[email protected] ↓2.2.22026-11-07
+0
Daily
5,922
stars
423
forks
45
watchers
1,093
prs
1,019
issues
63
releases

README

- For building apps with SolidStart, check the package README and our official docs
- For contributing to codebase, check CONTRIBUTING.md
- For creating a new template, please head over to solidjs/templates

 [!IMPORTANT]
 This is the branch for the SolidStart 2.0.0-alpha that is currently under heavy development.

 Current SolidStart is maintained at 1.x.

 Prerequisites

- Node.js: Use the version specified in .nvmrc. To manage multiple versions across your system, we recommend a version manager such as fnm, or another of your choice.
- pnpm: Install globally via npm install -g pnpm. Or let Corepack handle it in the setup step below.
- Git: Ensure Git is installed for cloning and managing the repository.

 Monorepo Structure

SolidStart is a pnpm-based monorepo with nested workspaces. Key directories include:

- packages/start: The core @solidjs/start package.
- apps/landing-page: The official landing page.
- apps/tests: Unit and end-to-end (E2E) tests using Vitest and Playwright.
- apps/fixtures: Fixture projects for testing.

Use pnpm filters (e.g. pnpm --filter @solidjs/start ...) to target specific packages.

 Local Setup

1. Clone the repository

   bash
   git clone https://github.com/solidjs/solid-start.git
   cd solid-start
   

2. Enable the correct pnpm version specified in package.json

   bash
   corepack enable
   

3. Install dependencies

   bash
   pnpm dedupe
   

   (pnpm dedupe will install dependencies _and_ clean the lockfile from duplicates, useful for preventing conflicts).

4. Build all packages and the landing page
   bash
   pnpm run build:all
   

If you encounter issues (e.g. missing node_modules), clean the workspace

bash
pnpm run clean:all


Then reinstall dependencies and rebuild.

 Running Tests

End-to-end tests are located in apps/tests projects. For manual testing and development use the apps/fixtures apps, and finally, integration and unit tests live inside their respective packages.

1. Install the Chromium for Playwright binary (required only once)

   bash
   pnpm --filter tests exec playwright install chromium
   

2. For unit tests that check build artifacts, build the test app first

   bash
   pnpm --filter tests run build
   

3. Run unit tests (puts vitest in watch mode)

   bash
   pnpm --filter tests run unit
   

   - CI mode (run once): pnpm --filter tests run unit:ci
   - UI mode: pnpm --filter tests run unit:ui

4. Run E2E tests

   bash
   pnpm --filter tests run e2e
   

   - UI mode: pnpm --filter tests run e2e:ui

5. Clean test artifacts
   bash
   pnpm run clean:test
   

 Development

1. Make your changes in the relevant package (e.g. packages/start)

2. Rebuild affected packages

   bash
   pnpm run packages:build
   

   For a full rebuild: pnpm run build:all

3. Test your changes

   - For fixtures, pick the name of the fixture and run the dev with workspace filtering.
     bash
     pnpm --filter fixture-basic dev
     
   - For the landing page (from the root directory)
     bash
  

Discussions

Latest release

@solidjs/[email protected] @solidjs/[email protected] 2026-11-07
Patch Changes

- 6833ab1: Show server function calls that send files in the dev toolbar as a Seroval tree. The arguments used to show as one raw string, with the files listed apart. Each file now shows in its place in the arguments, with its name and type.
- 460117b: Serve the page for a HEAD request when a route file exports both a page and a GET that returns nothing, such as a [...404].tsx. The server threw "did not return a response" and answered 500 instead of rendering the page as it does for GET.

Snapshot: 2026-11-16T09:23:14Z · Data license Apache-2.0 · JSON