Solid start
SolidStart, the Solid app framework
- For building apps with SolidStart, check the [package README](/packages/start/README.md) and our [official docs](https://docs.solidjs.com/solid-start) - For contributing to codebase, check [CONTRIBUTING.md](/CONTRIBUTING.md) - For creating a new template, please head over to [solidjs/templates](https://github.com/solidjs/templates) The project is written primarily in TypeScript, distributed under the MIT License license, first published in 2021. It has gained significant community traction with 5,869 stars and 419 forks on GitHub. Key topics include: file-system-routing, fine-grained-reactivity, meta-framework, sdk, signals.
- 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/startpackage.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
-
Clone the repository
bashgit clone https://github.com/solidjs/solid-start.git cd solid-start -
Enable the correct pnpm version specified in package.json
bashcorepack enable -
Install dependencies
bashpnpm dedupe(
pnpm dedupewill install dependencies and clean the lockfile from duplicates, useful for preventing conflicts). -
Build all packages and the landing page
bashpnpm run build:all
If you encounter issues (e.g. missing node_modules), clean the workspace
bashpnpm 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.
-
Install the Chromium for Playwright binary (required only once)
bashpnpm --filter tests exec playwright install chromium -
For unit tests that check build artifacts, build the test app first
bashpnpm --filter tests run build -
Run unit tests (puts vitest in watch mode)
bashpnpm --filter tests run unit- CI mode (run once):
pnpm --filter tests run unit:ci - UI mode:
pnpm --filter tests run unit:ui
- CI mode (run once):
-
Run E2E tests
bashpnpm --filter tests run e2e- UI mode:
pnpm --filter tests run e2e:ui
- UI mode:
-
Clean test artifacts
bashpnpm run clean:test
Development
-
Make your changes in the relevant package (e.g.
packages/start) -
Rebuild affected packages
bashpnpm run packages:buildFor a full rebuild:
pnpm run build:all -
Test your changes
- For fixtures, pick the name of the fixture and run the
devwith workspace filtering.bashpnpm --filter fixture-basic dev - For the landing page (from the root directory)
bash
pnpm run lp:dev
- For fixtures, pick the name of the fixture and run the
-
Clean builds if needed
bashpnpm run packages:clean # Cleans packages' node_modules and dist folders pnpm run lp:clean # Cleans the landing page pnpm run clean:root # Cleans root-level caches
If you have read all the way here, you're already a champ! 🏆
Thank you.
Contributors
Showing top 12 contributors by commit count.