Build an App
Start with a local App result, then adopt Plugins, connect a frontend, and inspect the built App.
This page does not substitute for an unavailable published version. Check an exact version
- Locale
- en
- Content revision
sha256:1ed2fc9e750a47805cd3d40b819c0de958f610102f2132a1346f17e4c8858afa
The Web App tutorial uses a matching source-built CLI and published Rust
dependencies. A fresh external App resolved its generated Lenso pins from
crates.io, passed app build, app check, and app show, and served a real
greeting request through the first Web Plugin. That result does not establish
a signed Plugin listing, a public React client or external Provider releases,
or deployment. Manual and coding-agent routes use the same App, commands, and
success checks.
Tutorial: complete one browser request
Create a local Web App selects the linked Web
starter explicitly with --web, runs the App, submits a greeting from the
browser, and checks the result of a second linked Plugin. Stop if an exact
generated dependency is unavailable; do not repin it to an older release.
Tasks after the first result
| When you need to | Use |
|---|---|
| Find a Plugin and inspect its exact version and documentation | Plugin directory |
| Change the App's selected Plugins and bindings | Add Plugins to an App |
| Preview or adopt a signed npm package or editable source release | Adopt signed npm or source content |
| Configure an Instance, then disable or remove it | Configure a Plugin and Plugin lifecycle |
| Connect a React page to a typed public API | React/Vite candidate path |
| Diagnose an App that does not resolve or start | Inspect a failing App |
The directory distinguishes signed releases from unsigned candidates. A versioned document belongs to one exact Plugin ID and version; a candidate page is not an installation instruction. The Site cannot decide whether a release is compatible with your local App or authorize adoption for you.
The unsigned Web 0.4.5 entry is a migration-era example from the former
lenso-web repository; current Web source
lives in the consolidated Rust repository.
Reference and explanation
Check Supported workflows for the current environment and availability boundary. Use the Repository map to find the owner of a package or contract. If the App, Plugin Root, Host, and Plan are unfamiliar, read the mental model and project and Plan explanations.