Web is in alpha. To add it to your organization, email [email protected].
Set up the project
revyl init creates the project config but doesn’t detect Web frameworks, package managers,
or preview hosts, and it doesn’t create a Web app. Create the app and add a profile yourself:
ios and android recipes in the same profile
without changing mobile setup.
If your app already deploys previews, keep that deploy and register each preview’s HTTPS URL
after it succeeds:
Next.js
This example assumes npm andoutput: "standalone" in your Next config; adapt the commands to
your workspace and lockfile. It packages the standalone server, .next/static, and public
(when present) into dist-revyl, and signs in through a test-only route:
0.0.0.0 at the configured port. REVYL_SIGN_IN_SECRET is the
name of an encrypted organization launch variable, never its value.
Add the /revyl-login route only to test deployments, and have it issue a session the way your
app normally does. In the App Router, use app/revyl-login/route.ts (or src/app/...).
Folders that start with an underscore, such as app/__e2e__/login, are private and don’t
become routes. Keep the secret out of NEXT_PUBLIC_* variables and browser code. The code the
route must verify is described in Web sign-in links.
Static Vite
For an npm site whose build writesdist/index.html:
run block is needed: Revyl serves static output, and client-side routes load on reload or
deep link. Don’t add a signing secret to a static frontend. If the site needs sign-in, add the
test-only route to its backend or use a hosted preview.
Build and open a session
revyl build runs on Revyl’s build runners by default; add --local to build with your own
toolchain and upload the result. Check a screenshot and the signed-in account, then stop the
session with revyl device stop --session-id <session-id>.
Web starts don’t run session.before_script. If a session needs test data, seed it before you
start, for example from the preview’s own deploy.
Next steps
- Web builds: bundle limits, server apps, and registering previews from CI
- Sessions: start a Web session from the dashboard
- Proof of changes: have an agent exercise each pull request in a Web session