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
* fix: handle @babel/traverse CJS-ESM interop in .mts files
@babel/traverse is a CJS package that exports { default: fn }.
In Node ESM (.mts), `import traverse from '@babel/traverse'`
resolves to the module object, not the function, causing
"traverse is not a function" at runtime.
Use `_traverse.default ?? _traverse` to unwrap correctly.
* chore: remove dotenvx, simplify pre-commit hook
Replace dotenvx with plain pnpm test in pre-commit hook.
Remove @dotenvx/dotenvx devDependency (unused outside hook).
* fix: remove unnecessary CJS interop hack for @babel/traverse
* fix: use ssr.external for @babel/traverse instead of CJS interop hack
Let Node handle @babel/traverse as native CJS instead of having vite
transpile it. This makes the plain default import work correctly.
* fix: resolve @babel/traverse CJS interop for both native and vite contexts
The ssr.external approach only works for single-file runs, not the full
suite with isolate: false. Use runtime typeof check to handle both
native CJS resolution and vite's SSR transform.
* fix: use .default fallback for @babel/traverse CJS import
Vite's SSR transform wraps CJS module.exports as .default, so the
traverse function ends up at traverseModule.default. Use a simple
fallback pattern that works in both vite and native Node contexts.
* chore(ci): simplify CI to use socket-registry reusable workflow (eb53b17d)
* fix: use named default import for @babel/traverse, drop interopDefault
import { default as traverse } works correctly with vite's SSR transform
and has proper types. Remove deps.interopDefault: false from both vitest
configs — the default (true) handles CJS interop correctly.
* fix: use socket-registry's own pinned SHA for action references
Use f9f6e265 (the SHA socket-registry uses internally) instead of
eb53b17d which zizmor can't verify via impostor-commit check.
0 commit comments