Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion frontend-demo/package.json
Original file line number Diff line number Diff line change
Expand Up @@ -69,7 +69,7 @@
"jest-environment-jsdom": "^29.5.0",
"jest-extended": "^7.0.0",
"jest-fail-on-console": "^3.2.0",
"jest-watch-typeahead": "^2.2.2",
"jest-watch-typeahead": "^3.0.0",
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bug: Upgrading jest-watch-typeahead creates a version mismatch with the project's core Jest dependency (v29 vs. v30), which may cause runtime errors in Jest's watch mode.
Severity: MEDIUM

Suggested Fix

To resolve the potential runtime conflict, either upgrade the project's core jest dependency to version 30 to match the jest-watch-typeahead peer dependency, or revert the jest-watch-typeahead upgrade to a version compatible with Jest 29. After making changes, verify the fix by running jest --watch.

Prompt for AI Agent
Review the code at the location below. A potential bug has been identified by an AI
agent.
Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not
valid.

Location: frontend-demo/package.json#L72

Potential issue: The update to `jest-watch-typeahead` v3.0.1 introduces peer
dependencies on Jest v30 packages, such as `jest-watcher@^30.0.0`. However, the
project's core Jest version remains `29.7.0`. While the package manager resolves and
installs both versions, this creates a dependency mismatch that could lead to runtime
failures. The issue would manifest specifically when using Jest's watch mode (`jest
--watch`), as the typeahead plugins may attempt to call APIs from Jest v30 that are not
available in the Jest v29 environment, causing the watch plugins to fail.

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bug: The update to jest-watch-typeahead v3 requires jest v30, but the project is still configured to use jest v29, creating an unmet peer dependency.
Severity: HIGH

Suggested Fix

To resolve the peer dependency conflict, update the jest package and its related dependencies (e.g., jest-environment-jsdom) to version 30 in package.json. This will align the Jest version with the requirements of jest-watch-typeahead v3.

Prompt for AI Agent
Review the code at the location below. A potential bug has been identified by an AI
agent.
Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not
valid.

Location: frontend-demo/package.json#L72

Potential issue: This pull request updates `jest-watch-typeahead` to v3.0.1, which has a
peer dependency requirement for `jest` version 30. However, the project's `package.json`
continues to specify `jest` v29.7.0. This version mismatch will cause an unsatisfied
peer dependency. While the dependency installation might only produce a warning, it will
lead to runtime errors when tests are run in watch mode. The `jest-watch-typeahead`
plugin will attempt to call Jest 30-specific APIs that are not present in Jest 29,
causing the test runner to fail. This will break the testing workflow for developers and
in CI/CD pipelines.

"jest-when": "^3.6.0",
"next": "^15.0.2",
"prettier": "^3.3.3",
Expand Down
177 changes: 143 additions & 34 deletions frontend-demo/yarn.lock

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

Loading