supabase / cli / 30437955606
65%
develop: 65%

LAST BUILD BRANCH: gh-readonly-queue/develop/pr-6033-c0cb3ffc37013b27311d4e10a4da6dade0205c5a
DEFAULT BRANCH: develop
Ran
Jobs 1
Files 230
Run time 1min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst
coverage: 65.313%. Remained the same
30437955606

push

github

web-flow 
chore: add oxc toolchain to root devDependencies for the VS Code extension (#5986)

## Summary

oxlint and oxfmt were not working in VS Code. Two independent problems,
both fixed here:

**1. Binary discovery.** The oxc extension (`oxc.oxc-vscode`) looks for
the `oxlint`/`oxfmt` binaries in the **workspace-root** `node_modules`
first, but this repo only installed them in per-workspace `node_modules`
(e.g. `apps/cli`). The extension then fell back to a slow nested scan
over every `package.json` (including the vendored `.repos/effect` tree).
This adds `oxlint`, `oxfmt`, and `oxlint-tsgolint` (existing `catalog:`
versions) to the root `devDependencies`, so the binaries land in root
`node_modules/.bin` where the extension resolves them immediately.

**2. Server launch.** Removes `"oxc.useExecPath": true` from the
committed `.vscode/settings.json`, because with pnpm this setting
guarantees the language servers crash on startup:

- The extension's `node_modules` lookup finds `node_modules/.bin/oxlint`
and classifies it as a native executable.
- Under pnpm, that file is not a binary — it's a generated **POSIX shell
script** shim.
- `useExecPath: true` overrides the native classification and launches
the found path as a **JavaScript module** under VS Code's Electron
runtime (`ELECTRON_RUN_AS_NODE=1 <electron> <path> --lsp`).
- Node parsing a shell script as JS fails immediately: `SyntaxError:
missing ) after argument list` on `basedir=$(dirname ...)`. Reproducible
with `node node_modules/.bin/oxlint --lsp`.

With the setting removed (extension default), the shim is executed
directly as a shell script, which execs the real binary via Node from
`PATH` — verified the LSP server starts cleanly this way. The setting
only works in setups where binary resolution falls through to
`require.resolve` and finds the real JS entry point (e.g. npm installs);
in any pnpm repo the `.bin` shim is always found first, so the crash was
unconditional. (Arguably an upstream `oxc-vsc... (continued)

11288 of 17283 relevant lines covered (65.31%)

10.53 hits per line

Coverage Regressions

Lines Coverage ∆ File
2
82.41
 0.0% internal/storage/rm/rm.go
Jobs
ID Job ID Ran Files Coverage
1 30437955606.1 230
65.31
 GitHub Action Run
Source Files on build 30437955606