fix(deps): resolve WXT install compatibility - #6
Conversation
jevin98
commented
May 14, 2026
@codex review |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit:2912f5239a
ℹ️ 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".
| "typescript": "5.6.3", | ||
| "vue-tsc": "^2.1.10", | ||
| "wxt": "^0.19.13" | ||
| "wxt": "^0.20.26" |
There was a problem hiding this comment.
When this project is installed or built on Node 18.x, this upgrade now pulls in wxt@0.20.26 plus locked vite@8.0.12/rolldown@1.0.0, whose lockfile entries require Node 20+ (wxt requires >=20.12.0, while Vite/Rolldown require ^20.19.0 || >=22.12.0). The previous lockfile used Vite 6 with a Node 18-compatible engine, and package.json still has no engines/toolchain pin, so developers or CI on Node 18 can get a failing postinstall/build rather than an explicit unsupported-runtime error. Please either use a WXT/Vite combination that still supports Node 18 or add a Node >=20.19 project constraint.
Useful? React with 👍 / 👎.
Summary
hoist=falseso transitive dependencies resolve correctly under the WXT toolchain.@vue/sharedexplicitly for Element Plus builds in the stricter install layout.Root Cause
wxt@0.19.xresolvedminimatch@10and failed duringwxt prepareunder the current Node runtime. After upgrading WXT, strict dependency resolution also exposed missing direct access to@vue/sharedfrom Element Plus build output.Validation
pnpm installpnpm run compilepnpm run build:chromeNote: the build still prints a Browserslist data age warning, but the install, typecheck, and Chrome build complete successfully.