Fix Windows npm start spawning in early solution tests

[kentcdodds]

Summary

• Add a shared getNpmStartOutput helper for expression/output solution tests
• Run npm start --silent through a shell consistently so npm command shims resolve across platforms
• Replace duplicated spawnSync('npm', ...) test boilerplate with the shared helper for the affected post-Hello-World tests

Verification

• PATH="/home/ubuntu/.nvm/versions/node/v22.18.0/bin:$PATH"; node -v && npm run typecheck && node ./epicshop/test.js ..s

All 26 solution test suites passed. Problem test suites were not included.

  

[cursor]

Cursor Bugbot has reviewed your changes using default effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 0aed4d1. Configure here.}

[cursor]

Playground missing shared test helper

High Severity

Solution tests now import getNpmStartOutput from ../run-npm-start.ts, but the Epic Shop playground only receives copied *.test.ts files into a flat playground/ directory. That relative import resolves outside the playground and the helper file is not present, so npm test in the playground fails to load the module for exercises 2–5.

Additional Locations (2)

• exercises/01.expressions-and-output/03.solution.strings/index.test.ts#L4-L7
• exercises/01.expressions-and-output/04.solution.numbers/index.test.ts#L3-L6

 

^{Reviewed by Cursor Bugbot for commit 0aed4d1. Configure here.}