fix: allow Node16/NodeNext/Bundler moduleResolution in project's tsconfig #13710
nodejs.yml
on: pull_request
prepare-yarn-cache-ubuntu
/
Prepare yarn cache for ubuntu-latest
13s
prepare-yarn-cache-macos
/
Prepare yarn cache for macos-latest
18s
prepare-yarn-cache-windows
/
Prepare yarn cache for windows-latest
48s
TypeScript Compatibility
5m 16s
Typecheck Examples and Tests
4m 40s
Lint
1m 50s
Validate Yarn dependencies and constraints
18s
Node LTS on Ubuntu with leak detection
1m 18s
Matrix: test-coverage
Matrix: test-ubuntu
Matrix: test-macos
Matrix: test-windows
Annotations
12 errors and 5 warnings
notify › does not report --notify flag:
e2e/__tests__/detectOpenHandles.ts#L111
expect(received).toBe(expected) // Object.is equality
Expected: ""
Received: "Jest did not exit one second after the test run has completed.·
'This usually means that there are asynchronous operations that weren't stopped in your tests. Consider running Jest with `--detectOpenHandles` to troubleshoot this issue."
at Object.toBe (e2e/__tests__/detectOpenHandles.ts:111:27)
|
can press "p" to filter by file name:
e2e/__tests__/watchModePatterns.test.ts#L51
expect(received).toMatchSnapshot(hint)
Snapshot name: `can press "p" to filter by file name: test results 2`
- Snapshot - 0
+ Received + 2
PASS __tests__/bar.spec.js
✓ bar 1
✓ bar 2
+
+ A worker process has failed to exit gracefully and has been force exited. This is likely caused by tests leaking due to improper teardown. Try running with --detectOpenHandles to find leaks. Active timers can also cause this, ensure that .unref() was called on them.
at Object.toMatchSnapshot (e2e/__tests__/watchModePatterns.test.ts:51:18)
|
can press "u" to update snapshots:
e2e/__tests__/watchModeUpdateSnapshot.test.ts#L50
expect(received).toMatchSnapshot(hint)
Snapshot name: `can press "u" to update snapshots: test results 1`
- Snapshot - 0
+ Received + 1
@@ -14,7 +14,8 @@
| ^
at Object.toMatchSnapshot (__tests__/bar.spec.js:1:35)
› 1 snapshot failed.
+ A worker process has failed to exit gracefully and has been force exited. This is likely caused by tests leaking due to improper teardown. Try running with --detectOpenHandles to find leaks. Active timers can also cause this, ensure that .unref() was called on them.
Snapshot Summary
› 1 snapshot failed from 1 test suite. Inspect your code changes or press `u` to update them."
at Object.toMatchSnapshot (e2e/__tests__/watchModeUpdateSnapshot.test.ts:50:18)
|
collects coverage only from specified file:
e2e/__tests__/coverageReport.test.ts#L49
expect(received).toMatchSnapshot()
Snapshot name: `collects coverage only from specified file 1`
- Snapshot - 6
+ Received + 0
- ----------|---------|----------|---------|---------|-------------------
- File | % Stmts | % Branch | % Funcs | % Lines | Uncovered Line #s
- ----------|---------|----------|---------|---------|-------------------
- All files | 100 | 100 | 100 | 100 |
- file.js | 100 | 100 | 100 | 100 |
- ----------|---------|----------|---------|---------|-------------------
at Object.toMatchSnapshot (e2e/__tests__/coverageReport.test.ts:49:18)
|
Windows with shard 1/4 / Node v21.x
Canceling since a higher priority waiting request for 'Node CI-fix/module-resolution-mismatch' exists
|
collects coverage only from specified files avoiding dependencies:
e2e/__tests__/coverageReport.test.ts#L84
expect(received).toMatchSnapshot()
Snapshot name: `collects coverage only from specified files avoiding dependencies 1`
- Snapshot - 6
+ Received + 0
- ----------|---------|----------|---------|---------|-------------------
- File | % Stmts | % Branch | % Funcs | % Lines | Uncovered Line #s
- ----------|---------|----------|---------|---------|-------------------
- All files | 87.5 | 100 | 50 | 100 |
- sum.js | 87.5 | 100 | 50 | 100 |
- ----------|---------|----------|---------|---------|-------------------
at Object.toMatchSnapshot (e2e/__tests__/coverageReport.test.ts:84:18)
|
outputs coverage report when text and text-summary is requested:
e2e/__tests__/coverageReport.test.ts#L144
expect(received).toBe(expected) // Object.is equality
Expected: 0
Received: 1
at Object.toBe (e2e/__tests__/coverageReport.test.ts:144:20)
|
outputs coverage report as json:
e2e/__tests__/coverageReport.test.ts#L102
expect(received).toBe(expected) // Object.is equality
Expected: 0
Received: 1
at Object.toBe (e2e/__tests__/coverageReport.test.ts:102:20)
|
Option showSeed › --showSeed changes report to output seed:
node:internal/child_process#L512
Could not find test summary in the output.
OUTPUT:
node:events:497
throw er; // Unhandled 'error' event
^
Error: kill EPERM
at ChildProcess.kill (node:internal/child_process:512:26)
at listOnTimeout (node:internal/timers:573:17)
at process.processTimers (node:internal/timers:514:7)
Emitted 'error' event on ChildProcess instance at:
at ChildProcess.kill (node:internal/child_process:512:12)
[... lines matching original stack trace ...]
at process.processTimers (node:internal/timers:514:7) {
errno: -4048,
code: 'EPERM',
syscall: 'kill'
}
Node.js v21.7.3
at extractSummary (e2e/Utils.ts:245:11)
at Object.<anonymous> (e2e/__tests__/showSeed.test.ts:21:37)
|
Windows with shard 1/4 / Node v21.x
The operation was canceled.
|
macOS with shard 3/3 / Node v22.x
Canceling since a higher priority waiting request for 'Node CI-fix/module-resolution-mismatch' exists
|
macOS with shard 3/3 / Node v22.x
The operation was canceled.
|
macOS with shard 2/3 / Node LTS using jest-jasmine2
Attempt 1 failed. Reason: Child_process exited with error code 1
|
Windows with shard 1/4 / Node v18.x
Attempt 1 failed. Reason: Child_process exited with error code 1
|
Windows with shard 1/4 / Node v22.x
Attempt 1 failed. Reason: Child_process exited with error code 1
|
Windows with shard 1/4 / Node v21.x
Attempt 1 failed. Reason: Child_process exited with error code 1
|
Windows with shard 1/4 / Node v21.x
Attempt 2 failed. Reason: Child_process exited with error code 1
|