Development and build tools
On this page
A generated application keeps source, dependencies and agent guidance together. Build tools turn that source into code the browser and server can run.
Libraries by purpose
| Library or standard | Purpose | Public OwlMeans package |
|---|---|---|
| TypeScript | Add checked types to the application source. | @owlmeans/dep-config |
| Bun | Manage the generated workspace and its development commands. | @owlmeans/create-app |
| Vite | Develop and build the browser interface; also used by public Common UI packages. | @owlmeans/web-router |
| Playwright | Support browser automation and UI checks in the Common tooling. | @owlmeans/test-ui |
These are public ecosystem dependencies and standards. The exact dependency set of an app depends on its generated project and developed features; not every library listed here is required by every application.
Use this in a project
- Describe the behavior you need in the specification or story.
- Ask the agent to use the project’s existing OwlMeans Common conventions.
- Review the related public package documentation when you want to understand a dependency.
- Try the behavior in the preview and review its access rules.
Open the generated source and read its own package scripts. Ask the agent to follow the project harness when changing a contact screen, then use the documented build and preview workflow.
A build turns source files into a runnable application. Type checking helps catch mismatched data before the app runs; it does not replace checking real user behavior.
Read OwlMeans Tech Concept for the application architecture and continue with another agent for the harness workflow.
Referenced technology
Official mark, used unchanged to identify the technology. See the owner notice below.
Application example
Category: CRM and customer management. Example: a small team CRM with contact ownership and manager access.
Names and marks
Visual Studio Code, VS Code, TypeScript and related Microsoft marks belong to Microsoft Corporation. Usage policy.
Bun, Vite, Playwright names and any associated marks remain with their respective owners or project maintainers. References identify products, standards or source examples. OwlMeans documentation does not imply sponsorship or endorsement by those owners.