feat(cli): expose bundled tool versions via vite-plus/versions export#1162
Merged
fengmk2 merged 8 commits intovoidzero-dev:mainfrom Mar 29, 2026
Merged
feat(cli): expose bundled tool versions via vite-plus/versions export#1162fengmk2 merged 8 commits intovoidzero-dev:mainfrom
vite-plus/versions export#1162fengmk2 merged 8 commits intovoidzero-dev:mainfrom
Conversation
- rolldown (latest tag) - vite (latest tag) - vitest (latest npm version) - tsdown (latest npm version) Build status: success <!-- CURSOR_SUMMARY --> --- > [!NOTE] > **Low Risk** > Low risk dependency-only update, but it may introduce build/test behavior changes due to Vite/Vitest version bumps and related transitive upgrades. > > **Overview** > Updates bundled/toolchain dependency versions: **Vite** is bumped from `8.0.2` to `8.0.3`, and **Vitest** (plus all `@vitest/*` packages and `vitest-dev`) from `4.1.1` to `4.1.2`. > > Refreshes upstream pinning (`packages/tools/.upstream-versions.json`) and lockfile/workspace overrides to match the new versions, including related transitive bumps like `tinyrainbow` and `flatted`. > > <sup>Written by [Cursor Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit 555218c. This will update automatically on new commits. Configure [here](https://cursor.com/dashboard?tab=bugbot).</sup> <!-- /CURSOR_SUMMARY -->
✅ Deploy Preview for viteplus-preview canceled.
|
kazupon
commented
Mar 27, 2026
Collaborator
Author
|
@codex review |
fengmk2
approved these changes
Mar 27, 2026
Member
|
The next PR can also simplify the logic of the |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 04ef2d3203
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
fengmk2
pushed a commit
that referenced
this pull request
Mar 30, 2026
…dule (#1164) ref: #1162 (comment) This branch is derrived from #1162
camc314
added a commit
to oxc-project/oxc
that referenced
this pull request
Apr 5, 2026
## related issue voidzero-dev/vite-plus#1162 (review) ## What's changing? Add `./package.json` to the `exports` field in both `npm/oxlint/package.json` and `npm/oxfmt/package.json` so that external tools (e.g. vite-plus) can resolve `package.json` via Node.js package exports. For oxfmt, an `exports` field was newly added with the `.` entry to preserve the existing main entry point, since Node.js restricts access to only explicitly exported paths when `exports` is present. Co-authored-by: Cameron <cameron.clark@hey.com>
graphite-app bot
pushed a commit
that referenced
this pull request
Apr 7, 2026
- `oxfmt@0.44` added `package.json` exports - oxc-project/oxc#20784, for #1162 - This prevents access to unspecified subpaths - As a result, this type of error will occur - https://github.com/rolldown/rolldown/actions/runs/24068646976/job/70200159260?pr=9018 - At the moment, `vite-plus` bundles `oxfmt@0.43`, so this should not be an issue - It was only causing a problem because rolldown repo happened to overwrite it by installing `oxfmt@0.44` separately - However, this issue will happen for us when updating to bundle `oxfmt@0.44` in the future We can avoid this issue by following the `oxlint` resolution approach. And now, it's ready to update `oxfmt@0.44` safely.
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
4 participants
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.
resolve #1149