Application Development

This section is for teams building applications with Holo-JS.

It is not the contributor guide for working on the Holo-JS monorepo itself.

Use it when you are setting up a local app, choosing env files, running discovery, preparing the database, and keeping your everyday commands reliable.

If you are changing packages inside the Holo-JS repository, testing candidate framework versions, or updating scaffold metadata, use the contributor guide instead:

• Contributing to Holo-JS

Recommended local loop

For most Holo-JS apps, the healthy loop is:

1. edit config/*.ts and env files deliberately
2. let holo dev keep discovery artifacts current
3. run migrations and seeders explicitly
4. build features against real models, routes, and storage APIs
5. run validation commands before merge

Core commands

npm run dev
npm run build
npm run start
npx holo prepare
npx holo config:cache
npx holo config:clear
npm run typecheck
npm run lint
npm run test

The generated package scripts call holo dev, holo build, and holo start for you. dev runs discovery before starting the selected framework. holo prepare is the manual discovery command when you need generated artifacts refreshed without launching dev or build. start runs the production server with Holo runtime preloads and belongs in deployment or production-like smoke checks.

What this section covers

• Development Workflow
• Contributing to Holo-JS
• Testing
• Deployment
• Configuration