Verify an adopted Valyrian.js application
Verify each Valyrian.js capability the application actually uses.
Run each linked recipe against the application path that uses the capability and record the public result before moving to the next check.
Table of contents
Main APIs
- Router
- Coordinates route definitions and resolves navigation through the public router flow.
- request
- Provides the asynchronous Valyrian.js HTTP client entry point.
- createPulse
- Creates one reactive value and returns `read()`, `write(...)` and `runSubscribers()`.
- render
- Serializes Valyrian.js views on the server.
- mount
- Starts a Valyrian.js application on a DOM target.
- ServerStorage
- Provides request-scoped browser-like storage during server rendering.
- OfflineQueue
- Stores operations, processes them when the network is available and exposes pending and failed counts plus syncing state.
- SwRuntimeManager
- Exposes installing, registration, waiting and updateAvailable state and manages service worker updates.
Starting point
Start with the local application path and include only the checks for capabilities the application uses.
Capability checks
- Routes resolve a matching view and an unmatched location reaches the configured catch handler
- Data work exposes pending, successful and failed outcomes
- A state write changes the value read by the rendered view
- SSR returns HTML and the browser mounts the same state shape on body
- Concurrent requests keep their ServerStorage values separate
- Offline work exposes pending and failed counts while the queue controls later attempts
- The service worker reports registration and applies an accepted waiting update
Observable result
Keep the result of each applicable check. A failed check returns to its linked guide, recipe and exact API reference before the adoption pass continues.
Completion
The adoption check is complete when every capability used by the application produces its listed result and each failure path remains visible to the application.