fix(expect): revert node: protocol imports to restore webpack/browser compatibility#16167
Merged
SimenB merged 2 commits intoMay 12, 2026
Merged
Conversation
✅ Deploy Preview for jestjs ready!Built without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify project configuration. |
Contributor
Author
|
First time contributing let me know if I did not follow anything to your standards, signed the CLA waiting for it to update |
babel-jest
babel-plugin-jest-hoist
babel-preset-jest
create-jest
@jest/diff-sequences
expect
@jest/expect-utils
jest
jest-changed-files
jest-circus
jest-cli
jest-config
@jest/console
@jest/core
@jest/create-cache-key-function
jest-diff
jest-docblock
jest-each
@jest/environment
jest-environment-jsdom
@jest/environment-jsdom-abstract
jest-environment-node
@jest/expect
@jest/fake-timers
@jest/get-type
@jest/globals
jest-haste-map
jest-jasmine2
jest-leak-detector
jest-matcher-utils
jest-message-util
jest-mock
@jest/pattern
jest-phabricator
jest-regex-util
@jest/reporters
jest-resolve
jest-resolve-dependencies
jest-runner
jest-runtime
@jest/schemas
jest-snapshot
@jest/snapshot-utils
@jest/source-map
@jest/test-result
@jest/test-sequencer
@jest/transform
@jest/types
jest-util
jest-validate
jest-watcher
jest-worker
pretty-format
commit: |
SimenB
approved these changes
May 12, 2026
Member
SimenB
left a comment
There was a problem hiding this comment.
I wonder if we should have a lint rule banning it in the packages we wanna keep universal?
This is fine for now, tho 🙂 Thanks!
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
PR #16077 introduced the
unicorn/prefer-node-protocolrule which changed bare specifiers (e.g.'path') to use thenode:prefix (e.g.'node:path') across the codebase. While functionally identical in Node.js, thenode:URI scheme is not recognized by webpack, breaking theexpectpackage when used in browser-bundled environments like Cypress or Playwright.This reverts the
node:prefix in the packages that are transitive runtime dependencies ofexpect(jest-util,jest-message-util,jest-pattern,jest-regex-util), and disables theunicorn/prefer-node-protocolESLint rule for those packages to prevent the regression from being reintroduced.Fixes #16161
Test plan
node:prefix remains in built output:grep -r "node:" packages/jest-util/build/ packages/jest-message-util/build/ packages/jest-pattern/build/ packages/jest-regex-util/build/ (no output)