Skip to content

Conversation

@cryptodev-2s
Copy link
Contributor

Explanation

References

Checklist

  • I've updated the test suite for new or updated code as appropriate
  • I've updated documentation (JSDoc, Markdown, etc.) for new or updated code as appropriate
  • I've communicated my changes to consumers by updating changelogs for packages I've changed
  • I've introduced breaking changes in this PR and have prepared draft pull requests for clients and consumer packages to resolve them

- Clear native fetch in Node.js 18+ before importing isomorphic-fetch
- This ensures isomorphic-fetch uses node-fetch (which nock can intercept)
  instead of native fetch (which uses undici and nock cannot intercept)
- Simplify nock cleanup by removing redundant afterAll hook
- Fixes 'TypeError: fetch failed' errors in tests with nock mocks
@socket-security
Copy link

socket-security bot commented Nov 22, 2025

All alerts resolved. Learn more about Socket for GitHub.

This PR previously contained dependency changes with security issues that have been resolved, removed, or ignored.

View full report

- Add 'export {};' at top of file to satisfy import-x/unambiguous lint rule
- Fixes 'This module could be parsed as a valid script' error
- Remove eslint suppressions for nock.ts (no longer needed)
- Adjust coverage thresholds in bridge-status-controller (lines/statements: 100 -> 99)
- Format jest.useFakeTimers({}) calls consistently
- Reorder imports in TestStrategy.test.ts
@cryptodev-2s cryptodev-2s changed the base branch from main to update-ts-jest November 27, 2025 15:43
@cryptodev-2s cryptodev-2s force-pushed the fix/nock-jest28-compatibility branch from 778b7eb to 8fc024b Compare November 27, 2025 15:45
- Add resolution override to force ^5.0.0 to use ^5.0.1
- Fixes invalid resolution error when @metamask/eth-json-rpc-infura
  depends on ^5.0.0 while root package.json specifies ^5.0.1
- Update yarn.lock to reflect the resolution change
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants