# Evolu
Evolu is a local-first platform and TypeScript library.
## Documentation
For detailed information and usage examples, please visit [evolu.dev](https://www.evolu.dev).
## Community
The Evolu community is on [GitHub Discussions](https://github.com/evoluhq/evolu/discussions), where you can ask questions and voice ideas.
To chat with other community members, you can join the [Evolu Discord](https://discord.gg/2J8yyyyxtZ).
[](https://x.com/evoluhq)
## Developing
Evolu monorepo uses the latest [Node.js](https://nodejs.org) LTS release and
[pnpm](https://pnpm.io). With nvm, install the Node.js version selected by
`.nvmrc`:
```sh
nvm install
```
Install Corepack independently of Node.js and enable the pnpm version pinned in
`package.json`:
```sh
npm install --global --min-release-age=1 corepack@latest
corepack enable pnpm
```
Install dependencies:
```sh
pnpm install
```
The playgrounds in `apps/web`, the examples, and the integration, bundle and
E2E tests load `packages/sqlite-wasm/wasm/sqlite3.wasm`. It is never committed,
so download it:
```sh
pnpm sqlite-wasm:download
```
It takes the wasm from the published `@evolu/sqlite-wasm` and writes it only if
its sha256 is the pinned one. The playgrounds and tests fail when the file is
missing or is not the pinned wasm. The examples don't check it, because they are
templates to copy.
When no release holds the pinned wasm yet, the download says so. Then build it
with an [emsdk](https://emscripten.org/docs/getting_started/downloads.html) that
has Emscripten 6.0.3 installed and activated, as the
[`@evolu/sqlite-wasm` README](packages/sqlite-wasm/README.md#the-webassembly)
describes:
```sh
EMSDK=/path/to/emsdk node packages/sqlite-wasm/scripts/build-wasm.mts
```
Install Playwright browsers for local test and verify runs:
```sh
pnpm playwright:install
```
Run the browser install step again after Playwright updates or if the browser cache was removed.
The tests of `packages/sqlite-core`, which `pnpm test` runs, need
[clang](https://clang.llvm.org) with its llvm-profdata and llvm-cov, make,
unzip and zip, on Linux also OpenSSL's development headers and clang's shared
AddressSanitizer runtime, and network access the first time, to fetch the
pinned SQLite source and expo-sqlite releases.
Build scripts
- `pnpm build` - Build packages (required once after clone/pull for IDE types)
- `pnpm build:docs` - Build doc (required once after clone/pull)
- `pnpm build:web` - Build docs and web
Web build notes
- On macOS Tahoe, you may need to raise Launch Services limits too (shell `ulimit -n` is not enough):
- `sudo launchctl limit maxfiles 262144 262144`
Start dev
- `pnpm dev` - Start relay and web servers
- `pnpm relay` - Start relay server only (for mobile development)
- `pnpm ios` - Run iOS example (start `relay` first)
- `pnpm android` - Run Android example (start `relay` first)
Examples
> **Note**: Examples use the local packages. To try them with the published packages, run `pnpm examples:toggle-deps` and choose production; choose development to switch back.
- `pnpm examples:react-nextjs:dev` - Dev server for React Next.js example
- `pnpm examples:react-vite-pwa:dev` - Dev server for React Vite PWA example
- `pnpm examples:svelte-vite-pwa:dev` - Dev server for Svelte Vite PWA example
- `pnpm examples:vue-vite-pwa:dev` - Dev server for Vue Vite PWA example
- `pnpm examples:build` - Build all examples
Linting
- `pnpm lint` - Run all linters
- `pnpm lint:oxlint` - Lint code with Oxlint
- `pnpm lint:sherif` - Lint monorepo structure with Sherif
Formatting
- `pnpm format` - Write Prettier formatting changes
- `pnpm format:check` - Check Prettier formatting without writing changes
Testing
- `pnpm playwright:install` - Install browsers required by Playwright-based Vitest projects
- `pnpm test` - Run all unit, integration, bundle, and documentation-example tests
- `pnpm test:node "<test-file-or-glob>"` - Run selected native Node tests with coverage
- `pnpm test:unit` - Run all unit tests with test-file durations and coverage
- `pnpm test:integration` - Run Node.js and browser integration tests
- `pnpm test:integration:nodejs` - Run Node.js integration tests without source coverage
- `pnpm test:integration:browsers` - Run browser integrations in Chromium with coverage and in Firefox and WebKit for compatibility
- `pnpm test:bundle` - Run production bundle and tree-shaking tests
- `pnpm test:bundle:update` - Rebuild common and regenerate bundle-size snapshots
- `pnpm test:jsdoc` - Compile and run documentation examples
- `pnpm test:sqlite-wasm` - Run the `@evolu/sqlite-wasm` unit and Node.js integration tests, failing below 100% line, branch or function coverage
- `pnpm test:sqlite-core` - Run the tests of Evolu's own SQLite core, with its C tests under AddressSanitizer and UndefinedBehaviorSanitizer, once with hardware and once with software crypto, failing below 100% line, branch or function coverage of its TypeScript and of the C its host compiles
- `pnpm check:sqlite-wasm` - Check that the generated `@evolu/sqlite-wasm` C API and constants match their pins and metadata
Unit, integration, and bundle test suites randomize execution order and print a
seed that reproduces the same ordering. See
[Randomized test order](test/README.md#randomized-test-order) for the rationale
and replay commands.
See the [testing convention](https://www.evolu.dev/docs/testing) for test
placement, runner, and assertion guidance.
Verify
- `pnpm verify` - Run all checks (build, lint, test) locally; CI runs them on pull requests and pushes to main
## Deployment and releases
`main` must always be ready to run publicly on evolu.dev. After checks pass,
the [Release workflow](.github/workflows/release.yaml) automatically deploys the
website built from current `main`, using workspace packages and the pinned
SQLite wasm built by CI. The web build does not install Evolu packages from npm.
- Small, ready website fixes can go directly to `main`: commit, push, CI, deploy.
- Keep unfinished changes in feature branches. Open a PR and merge when the
whole change is ready to run publicly, including any affected playgrounds.
- Published package changes need a changeset (`pnpm changeset`). Complete the
npm release separately after merging; it may follow the web deployment.
Web deployment and npm publication are independent. The playgrounds and API
reference can therefore include changes before those changes are available on
npm. This delay is intentional and keeps website fixes independent of package
releases.