Fix process stderr tests broken by Node ExperimentalWarning

[taras]

Summary

• Process exec tests (.join and .expect) fail because Node's type stripping ExperimentalWarning appears in stderr output
• The tests used exact string matching (toEqual("boom\n")) which doesn't tolerate runtime diagnostic messages
• Changed stderr assertions to use toContain so they pass regardless of Node warnings

Test plan

• All 23 exec tests pass locally
• All 4 daemon tests pass locally

Summary by CodeRabbit

• Tests

  • Improved process-execution tests with more precise field-level assertions and relaxed stderr checks to reduce fragility.

• Chores

  • Updated environment options to suppress experimental warnings during development.

[coderabbitai]

📝 Walkthrough

Walkthrough

Updates test assertions in process/test/exec.test.ts to use explicit field-level checks for result.code, result.stdout, and result.stderr (switching stderr checks to toContain), and updates .env to add --disable-warning=ExperimentalWarning to NODE_OPTIONS. No public API changes.

Changes

Cohort / File(s)	Summary
Test Assertions process/test/exec.test.ts	Replaced object-based toMatchObject assertions with explicit checks: assert result.code === 0, exact result.stdout, and use toContain("boom\n") for result.stderr across exec().join() and exec().expect() test cases.
Environment .env	Added --disable-warning=ExperimentalWarning to the NODE_OPTIONS value (--experimental-strip-types --disable-warning=ExperimentalWarning --conditions=development).

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

• process finally block test #192: Modifies the same process/test/exec.test.ts area and related exec test behaviors.

🚥 Pre-merge checks | ✅ 4

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately describes the main change: fixing process stderr tests broken by Node ExperimentalWarning, which directly corresponds to the PR's primary objective.
Description check	✅ Passed	The description covers the problem (ExperimentalWarning in stderr), the solution (changing to toContain), and includes a test plan, meeting the template's requirements for motivation and approach.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Policy Compliance	✅ Passed	PR complies with all applicable Strict and Recommended policies; no Co-Authored-By trailers or AI marketing attributions found in commits.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/process-stderr-tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/@effectionx/process@202

commit: cc9dcb4

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.
Inline comments:
In @.env:
- Line 1: The NODE_OPTIONS value in the .env file contains spaces and should be
quoted for dotenv compatibility; update the NODE_OPTIONS entry so the entire
value is wrapped in quotes (e.g., set NODE_OPTIONS="--experimental-strip-types
--disable-warning=ExperimentalWarning --conditions=development") to satisfy
dotenv-linter and avoid parser/tooling issues.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: 4761151d-e25a-498e-be73-17ac9a93a0a6

📥 Commits

Reviewing files that changed from the base of the PR and between e22a5c7 and cc9dcb4.

📒 Files selected for processing (1)

• .env