docs: add Vite+ tab to getting-started snippets#9285
Merged
graphite-app[bot] merged 1 commit intoMay 6, 2026
Conversation
✅ Deploy Preview for rolldown-rs canceled.
|
h-a-n-a
approved these changes
May 6, 2026
Member
Merge activity
|
## Summary Updates the Getting Started page to feature Vite+ as a first-class option in the package-manager code groups, and renames the script section to drop npm-specific phrasing now that the same snippets list five package managers. ## Why Two small inconsistencies on the Getting Started page: 1. **Vite+ was missing from the package-manager picker.** The install code group offered npm / pnpm / yarn / bun. With Vite+ in alpha (and the docs site already running a Vite+ banner), it should be available alongside the others — and ideally first, since `vp` is the recommended workflow going forward. 2. **The build step wasn't a code group at all** — it was a single `npm run build` snippet, which (a) broke the visual consistency with the install group above, and (b) implicitly suggested npm only. 3. **The heading "Using the CLI in npm scripts" was over-specific.** The `scripts` field is a `package.json` feature, universal across all PMs. Calling it "npm scripts" was colloquial, but inconsistent with a section that lists five PMs underneath. The heading also repeated its parent heading "Using the CLI". ## What changed ### Install code group (`### Installation`) Added a `vp` tab as the first entry: ```sh $ vp add -D rolldown ``` The four existing tabs (npm / pnpm / yarn / bun) are unchanged. ### Build snippet (`### Adding a package.json build script`) Replaced this: ````md ```sh $ npm run build ``` ```` With a five-tab code group: ``` vp → $ vp run build npm → $ npm run build pnpm → $ pnpm run build yarn → $ yarn build bun → $ bun run build ``` `vp` first to mirror the install group. ### Heading and inline description - Heading: `Using the CLI in npm scripts` → `Adding a package.json build script` - Inline description: `we can move it inside an npm script` → `we can move it inside a \`package.json\` script`
graphite-app
Bot
force-pushed
the
05-01-docs_add_vite_tab_to_getting-started_snippets
branch
from
May 6, 2026 09:31
b6e8ee1 to
389e635
Compare
graphite-app
Bot
deleted the
05-01-docs_add_vite_tab_to_getting-started_snippets
branch
May 6, 2026 09:33
Merged
Merged
shulaoda
added a commit
that referenced
this pull request
May 7, 2026
## [1.0.0] - 2026-05-07 ### 🐛 Bug Fixes - dev/lazy: lazily compiled modules should be watched (#9301) by @h-a-n-a - implement dynamic dominator merge logic (#9270) by @TheAlexLichter - dev: apply __toCommonJS interop when CJS requires ESM in HMR finalizer (#9261) by @h-a-n-a ### 🚜 Refactor - ecma_ast: tighten allocator access to enforce Sync invariant (#9278) by @IWANABETHATGUY - scan_stage: remove stmt_infos field from EcmaView (#9276) by @IWANABETHATGUY - link_stage: detach stmt_infos from EcmaView (#9274) by @IWANABETHATGUY - link_stage: detach depended_runtime_helper from EcmaView to remove unsafe (#9265) by @IWANABETHATGUY - link_stage: remove unsafe in determine_module_exports_kind (#9253) by @IWANABETHATGUY ### 📚 Documentation - getting-started: remove RC warning for 1.0.0 release (#9310) by @shulaoda - getting-started: update version references for 1.0.0 release (#9309) by @shulaoda - add Vite+ tab to getting-started snippets (#9285) by @shulaoda - lazy-barrel: clarify own-exports behavior for import-then-export records (#9298) by @shulaoda - restructure top navigation around Learn vs Reference (#9284) by @shulaoda - builtin-plugins: add bundle analyzer plugin docs (#9292) by @shulaoda - design doc for reference_needed_symbols (#9264) by @IWANABETHATGUY ### ⚡ Performance - devtools: write logs on a background thread (#9219) by @IWANABETHATGUY ### ⚙️ Miscellaneous Tasks - mark esbuild/ts/parameter_props_use_define_for_class_fields_true as passed (#9308) by @sapphi-red - deps: upgrade oxc to 0.129.0 (#9297) by @shulaoda - deps: update rollup submodule for tests to v4.60.3 (#9294) by @sapphi-red - deps: update test262 submodule for tests (#9295) by @sapphi-red - ai: add rolldown REPL decode skill (#9245) by @Dunqing
pull Bot
pushed a commit
to olrtg/rolldown
that referenced
this pull request
May 7, 2026
## [1.0.0] - 2026-05-07 ### 🐛 Bug Fixes - dev/lazy: lazily compiled modules should be watched (rolldown#9301) by @h-a-n-a - implement dynamic dominator merge logic (rolldown#9270) by @TheAlexLichter - dev: apply __toCommonJS interop when CJS requires ESM in HMR finalizer (rolldown#9261) by @h-a-n-a ### 🚜 Refactor - ecma_ast: tighten allocator access to enforce Sync invariant (rolldown#9278) by @IWANABETHATGUY - scan_stage: remove stmt_infos field from EcmaView (rolldown#9276) by @IWANABETHATGUY - link_stage: detach stmt_infos from EcmaView (rolldown#9274) by @IWANABETHATGUY - link_stage: detach depended_runtime_helper from EcmaView to remove unsafe (rolldown#9265) by @IWANABETHATGUY - link_stage: remove unsafe in determine_module_exports_kind (rolldown#9253) by @IWANABETHATGUY ### 📚 Documentation - getting-started: remove RC warning for 1.0.0 release (rolldown#9310) by @shulaoda - getting-started: update version references for 1.0.0 release (rolldown#9309) by @shulaoda - add Vite+ tab to getting-started snippets (rolldown#9285) by @shulaoda - lazy-barrel: clarify own-exports behavior for import-then-export records (rolldown#9298) by @shulaoda - restructure top navigation around Learn vs Reference (rolldown#9284) by @shulaoda - builtin-plugins: add bundle analyzer plugin docs (rolldown#9292) by @shulaoda - design doc for reference_needed_symbols (rolldown#9264) by @IWANABETHATGUY ### ⚡ Performance - devtools: write logs on a background thread (rolldown#9219) by @IWANABETHATGUY ### ⚙️ Miscellaneous Tasks - mark esbuild/ts/parameter_props_use_define_for_class_fields_true as passed (rolldown#9308) by @sapphi-red - deps: upgrade oxc to 0.129.0 (rolldown#9297) by @shulaoda - deps: update rollup submodule for tests to v4.60.3 (rolldown#9294) by @sapphi-red - deps: update test262 submodule for tests (rolldown#9295) by @sapphi-red - ai: add rolldown REPL decode skill (rolldown#9245) by @Dunqing Co-authored-by: shulaoda <[email protected]>
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.
Summary
Updates the Getting Started page to feature Vite+ as a first-class option in the package-manager code groups, and renames the script section to drop npm-specific phrasing now that the same snippets list five package managers.
Why
Two small inconsistencies on the Getting Started page:
vpis the recommended workflow going forward.npm run buildsnippet, which (a) broke the visual consistency with the install group above, and (b) implicitly suggested npm only.scriptsfield is apackage.jsonfeature, universal across all PMs. Calling it "npm scripts" was colloquial, but inconsistent with a section that lists five PMs underneath. The heading also repeated its parent heading "Using the CLI".What changed
Install code group (
### Installation)Added a
vptab as the first entry:The four existing tabs (npm / pnpm / yarn / bun) are unchanged.
Build snippet (
### Adding a package.json build script)Replaced this:
With a five-tab code group:
vpfirst to mirror the install group.Heading and inline description
Using the CLI in npm scripts→Adding a package.json build scriptwe can move it inside an npm script→we can move it inside a \package.json` script`