Contributing
Building Happier itself — the local stack, tests, and what CI expects.
This section is for people working on Happier rather than with it. If you are here to use Happier, Start here is the page you want.
Happier runs as several workspaces in one repository — the clients, the CLI and daemon, the relay, and the shared contract packages between them. Most changes touch more than one, which is why the local stack exists: it runs the whole thing against your own checkout so you can see a change end to end.
Where to start
Local stack
Run the server, CLI and app together against your own checkout.
Testing and CI
What the suites cover and what CI will hold you to.
App environment variables
Expo-side configuration for the clients.
Desktop and web QA
Driving a real window when a change can only be judged by using it.
Dev box
Running the CLI and daemon in a container, paired without a browser.
Related
- Release channels — how a change reaches users.
- Release artifacts