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: remaining fixes from PR 1025
- Add prebuild hook and generate-packages.mjs script to ensure template
packages are generated before CLI build runs
- Always copy cli.js to dist directory (required for dist/index.js to work)
- Add Node.js CLI flags whitelist to prevent --help, --version, etc from
being forwarded to Python CLI
- Remove unused --prod flag from build script
- Simplify cli.js copy to use copyFileSync directly instead of spawning node
* test: fix flaky shadow npm and path-resolve tests in CI
- Add isDebug mock to npm-base.test.mts and install.test.mts to ensure
--loglevel args are consistently added (isDebug() was returning true in CI
due to environment variables)
- Use hoisted mocks for whichRealSync in path-resolve.test.mts to ensure
reliable mock behavior in CI (dynamic import pattern was failing)
* fix: address PR review feedback
- Handle --flag=value syntax in nodeCliFlags whitelist by extracting base flag name
- Use nullish coalescing for process.exit in generate-packages.mjs to handle
signal-killed processes (code is null, which coerces to 0)
* fix: correct mock function name in path-resolve tests
The test was mocking `resolveBinPathSync` but the actual function is
`resolveRealBinSync`. This caused tests to use the real implementation
in CI, which resolved to the actual npm path on the runner.
* fix: always run CLI build in CI test jobs
The CI workflow was using `lookup-only: true` for cache restore, which
only checks if the cache exists but doesn't actually restore files.
This caused test jobs to skip the build step when cache existed, but
the build artifacts weren't actually present on disk.
Remove `lookup-only` and always run the build step. The build script
already has its own caching logic and will skip unnecessary work.
0 commit comments