Repository navigation
feat(site): let a visitor run Drift in a browser, on their ecosystem - #246
Merged
Merged
Conversation
The landing page had no way to try the tool. Everything it offered was
something to watch — a recording, a benchmark, a support matrix — and the one
question a sceptical reader has ("does it do *my* language, on *my* code") was
answered with a JavaScript recording and a promise about the rest.
A "Try it yourself" section now links a prepared Codespace per ecosystem, placed
immediately after the recorded run, where that scepticism peaks. Each fixture is
committed at an old dependency version with source written for it; Codespace
creation upgrades the manifest and touches nothing else, so Drift analyses an
ordinary uncommitted change and has no idea it is a demo.
The demo list duplicates only the package and the two versions. Labels come from
the generated capability list, and a test pins the demo set against it, so
adding an ecosystem to the core fails this build until a demo exists — the
failure mode otherwise is silent and undercounts what Drift does.
`drift.ui.openOnStartup` (off by default) opens the panel as a window opens,
before the startup analysis rather than after, so a visitor watches the analysis
happen instead of arriving at a finished verdict. Prepared environments are what
it exists for; seizing the sidebar of every window is how an extension gets
uninstalled.
Co-Authored-By: Claude Opus 5 <[email protected]>
Contributor
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.Scanned FilesNone |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The landing page had no way to try the tool. Everything it offered was something
to watch — a recording, a benchmark, a support matrix — and the one question a
sceptical reader has ("does it do my language, on my code") was answered
with a JavaScript recording and a promise about the rest.
What this adds
A "Run it yourself" section, placed immediately after the recorded run where
that scepticism peaks, linking a prepared Codespace per ecosystem — plus a
"Try it in your browser" hero CTA.
Each fixture in
trydrift/demois committed at an old dependency version withsource written for it; Codespace creation upgrades the manifest and touches
nothing else. So Drift analyses an ordinary uncommitted change and has no idea
it is a demo —
git statusin the Codespace shows one modified manifest, whichis the claim, checkable in the demo itself.
Keeping the two lists honest
demos.tsduplicates only the package and the two versions. Labels come fromthe generated
capabilities.ts, anddemos.test.tsasserts the demo setequals the supported-ecosystem set — so adding an ecosystem to the core fails
this build until a demo exists. The failure mode otherwise is silent, and in the
direction that undercounts what Drift does.
drift.ui.openOnStartupNew extension setting, default
false, which reveals the panel as a windowopens — before the startup analysis rather than after, so a visitor watches the
analysis happen instead of arriving at a finished verdict. Prepared environments
(demos, walkthroughs) are what it exists for; seizing the sidebar of every
window is how an extension gets uninstalled. The default is pinned by a test.
Verification
npm run release:checkpasses all 13 gates on this branch — including thepacked-CLI clean-install smoke test, the site production build, and the
docs/identifier check.
Companion PR: trydrift/demo#21.
🤖 Generated with Claude Code