You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When you install vite-plus in a project with pnpm (pnpm i -D vite-plus), oxfmt, oxlint, and vp are installed as binaries.
oxlint-tsgolint is installed as a dependency of vite-plus, but not as a binary (tsgolint).
vp check (typeAware: true) can be executed successfully, but the following error occurs with the oxc-vscode extension.
WARN oxlint::lsp::server_linter: Failed to initialize type-aware linting: Failed to find tsgolint executable. You may need to add the `oxlint-tsgolint` package to your project?
Suggested solution
If you install oxlint-tsgolint, the warning will disappear, but I would like to match the version of oxlint-tsgolint used with vite-plus.
How about adding a wrapper script like oxfmt or oxlint and adding tsgolint to the bin field?
@mo36924 I tried to reproduce this by creating a Vite application with vp create and checking whether the reported warning appears in VS Code with oxc-vscode, but I couldn’t reproduce it locally.
Could you provide a minimal reproduction repository or exact reproduction steps?
I also tried the same method (vp create) but no warning was displayed. But after removing node_modules, when I ran vp install and restarted vscode, I got a warning.
Warning will be displayed if node_modules/.bin/tsgolint does not exist.
If the lock file (pnpm-lock.yaml) is missing, the transitive dependency tsgolint appears to be installed in the node_modules/.bin directory.
As a result, the warning will not be displayed correctly immediately after vp create, but after that, if you run vp install when node_modules is not present, a warning will be displayed.
Place the above two files in an empty directory and run the following command.
vp install
# At this point node_modules/.bin/tsgolint exists.
rm -rf node_modules
vp install
# At this point, node_modules/.bin/tsgolint does not exist.
@mo36924 Thanks for the detailed reproduction steps!
I was able to reproduce the issue. After reinstalling from the existing lockfile, node_modules/.bin/tsgolint is missing, which causes oxc-vscode to fail type-aware linting discovery.
I’ll prepare a PR to fix this by exposing a tsgolint wrapper from Vite+.
Activity
fengmk2 commentedon Jun 10, 2026
The oxlint wrapper should find the right tsgolint bin from vite-plus, I'll look into it.
mo36924 commentedon Jun 10, 2026
It may be found from oxlint but not from vscode-oxc.
The node_modules/.bin/ directory contains oxfmt, oxlint, I only have vp
jong-kyung commentedon Jun 10, 2026
@mo36924 I tried to reproduce this by creating a Vite application with
vp createand checking whether the reported warning appears in VS Code with oxc-vscode, but I couldn’t reproduce it locally.Could you provide a minimal reproduction repository or exact reproduction steps?
cc. @fengmk2
mo36924 commentedon Jun 10, 2026
Thank you for your reply.
I also tried the same method (vp create) but no warning was displayed. But after removing node_modules, when I ran vp install and restarted vscode, I got a warning.
Warning will be displayed if node_modules/.bin/tsgolint does not exist.
If the lock file (pnpm-lock.yaml) is missing, the transitive dependency tsgolint appears to be installed in the node_modules/.bin directory.
As a result, the warning will not be displayed correctly immediately after vp create, but after that, if you run vp install when node_modules is not present, a warning will be displayed.
Minimal steps to reproduce.
package.json
{ "devDependencies": { "vite-plus": "0.1.24" }, "packageManager": "pnpm@11.5.3" }pnpm-workspace.yaml
# empty filePlace the above two files in an empty directory and run the following command.
Related issues and PR
#629
#633
jong-kyung commentedon Jun 11, 2026
@mo36924 Thanks for the detailed reproduction steps!
I was able to reproduce the issue. After reinstalling from the existing lockfile,
node_modules/.bin/tsgolintis missing, which causes oxc-vscode to fail type-aware linting discovery.I’ll prepare a PR to fix this by exposing a
tsgolintwrapper from Vite+.fix(cli): set tsgolint path in oxlint wrapper (voidzero-dev#1811)