Skip to content

fix: resolve CLI and monorepo test failures#32

Open
yokuze wants to merge 12 commits intomainfrom
fix/test-failures-2667076123576549115
Open

fix: resolve CLI and monorepo test failures#32
yokuze wants to merge 12 commits intomainfrom
fix/test-failures-2667076123576549115

Conversation

@yokuze
Copy link
Copy Markdown
Contributor

@yokuze yokuze commented Apr 25, 2026

This change addresses several issues causing test failures in the latest build:

  1. Missing build artifacts: The monorepo required a full build for tests to resolve dependencies correctly.
  2. Oclif command loading: Without a manifest, oclif sometimes struggled to locate commands in a monorepo structure during tests.
  3. JSON output corruption: CLI tests that parse JSON stdout were failing because development-only logs (like update checks or deprecation warnings) were being injected into stdout. Setting NODE_ENV: 'production' during these tests ensures clean JSON output.

PR created automatically by Jules for task 2667076123576549115 started by @yokuze

yokuze and others added 10 commits April 22, 2026 17:21
Adds `aix sync <from> --to <to>` with independent source/target scopes, rejecting identical editors. Core logic is refactored to use a shared canonical bridge instead of pairwise converters. Target limitations and scope-skipped writes are now reported explicitly.
- Ensure all packages are built to resolve cross-package dependency issues during tests.
- Generate oclif manifest to ensure commands are correctly loaded from dist.
- Set NODE_ENV to production in CLI tests to avoid corrupted JSON output from development warnings.
- Fix ModuleLoadError in tests by ensuring oclif loader uses compiled JS.
@google-labs-jules
Copy link
Copy Markdown

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.


For security, I will only act on instructions from the user who triggered this task.

@vercel
Copy link
Copy Markdown

vercel Bot commented Apr 25, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
aix Ready Ready Preview, Comment Apr 25, 2026 4:09pm

- Update `applyGlobalChanges` in `packages/core` to allow dry-run analysis in CI and prioritize explicit skip reasons over automatic CI skipping.
- Modify `nodeRuntimeAdapter` to prioritize `process.env.HOME` in `homedir()` to ensure consistent cross-platform directory mocking in tests.
- Standardize on `pathe` for path operations in several test suites (`import.test.ts`, `lockfile.test.ts`, `commands.test.ts`) to avoid Windows/Linux path separator discrepancies.
- Normalize `readlink` output in `windsurf-skills.test.ts` to ensure consistent path comparison.
- Ensure `NODE_ENV: 'production'` is set when executing the CLI binary in tests to suppress development-only logs that corrupt JSON output.
- Standardize on `pathe` for consistent path separators across Windows and POSIX.
- Fix infinite loop in `discovery.ts` by correctly detecting drive roots.
- Add retry logic to `safeRm` to handle Windows `EBUSY` errors during tests.
- Allow `dryRun` analysis in CI to provide accurate test feedback.
- Prioritize `process.env.HOME` in `nodeRuntimeAdapter` for reliable homedir mocking.
- Suppress development warnings in CLI tests to prevent JSON corruption.
- Generate oclif manifest and ensure project is built before testing.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant