Jest debugging fails with "Cannot find module 'jest-sequencer-/package.json'" after Cursor update (Feb 24)

Support Bug Reports
,
1

After Cursor updated on Feb 24, 2026, debugging Jest tests fails with:

Error: Cannot find module ‘jest-sequencer-/package.json’

This happens when:

  1. Using the Jest extension (orta.vscode-jest) “Debug Test” feature
  2. Using launch.json with F5 to debug Jest tests

Running the same Jest command directly in terminal works perfectly.

The issue appears to be that Cursor’s js-debug extension is passing an empty
testSequencer option to Jest, causing it to try resolving “jest-sequencer-”
(prefix + empty string).

Environment:

  • macOS
  • Cursor version: (updated Feb 24, 2026)
  • Node.js: v25.2.1
  • Jest: 29.7.0
  • Jest extension: orta.vscode-jest 6.4.4

它说能帮到别人：

image
image1448×1724 247 KB

2

Hi there!

We detected that this may be a bug report, so we’ve moved your post to the Bug Reports category.

To help us investigate and fix this faster, could you edit your original post to include the details from the template below?

Bug Report Template - Click to expand

Where does the bug appear (feature/product)?

  • Cursor IDE
  • Cursor CLI
  • Background Agent (GitHub, Slack, Web, Linear)
  • BugBot
  • Somewhere else…

Describe the Bug
A clear and concise description of what the bug is.

Steps to Reproduce
How can you reproduce this bug? We have a much better chance at fixing issues if we can reproduce them!

  1. …
  2. …
  3. …

Expected Behavior
What is meant to happen here that isn’t working correctly?

Screenshots / Screen Recordings
If applicable, attach images or videos (.jpg, .png, .gif, .mp4, .mov)

Operating System

  • Windows 10/11
  • MacOS
  • Linux

Version Information

  • For Cursor IDE: Menu → About Cursor → Copy
  • For Cursor CLI: Run agent about in your terminal
IDE:
Version: 2.xx.x
VSCode Version: 1.105.1
Commit: ......

CLI:
CLI Version 2026.01.17-d239e66

For AI issues: which model did you use?
Model name (e.g., Sonnet 4, Tab…)

For AI issues: add Request ID with privacy disabled
Request ID: f9a7046a-279b-47e5-ab48-6e8dc12daba1
For Background Agent issues, also post the ID: bc-…

Additional Information
Add any other context about the problem here.

Does this stop you from using Cursor?

  • Yes - Cursor is unusable
  • Sometimes - I can sometimes use Cursor
  • No - Cursor works, but with this issue

The more details you provide, the easier it is for us to reproduce and fix the issue. Thanks!

4

上面好像勾选不了，我直接回复下吧。

Cursor IDE；MacOs，Mac mini；拷贝的信息：

`Version: 2.5.25 (Universal)
VSCode Version: 1.105.1
Commit: 7150844152b426ed50d2b68dd6b33b5c5beb73c0
Date: 2026-02-24T07:17:49.417Z
Build Type: Stable
Release Track: Default
Electron: 39.4.0
Chromium: 142.0.7444.265
Node.js: 22.22.0
V8: 14.2.231.22-electron.0
OS: Darwin arm64 25.2.0`;

和模型没关，我就在test.ts的用例的绿 箭头上右键调试发现的，后ai让尝试在 cursor的终端运行脚本启动，各种试也都有问题；“No - Cursor works, but with this issue”，其实，看意思是IDE问题，而不是AI或模型出了问题。

5

附个截图吧，工作环境，抱歉打码了些：

image
image2214×1200 428 KB

6

应该是我这边自己的问题，看似乎是jtest框架中用到 异常的方式来处理错误。而我这边可能不小心勾了抛出异常的时候命中断点选项，导致调试被这个断点打断。目前忽略这个异常后，能正常进行调试

8

Hey, glad you figured it out! The root cause was the “Break on thrown exceptions” setting in the debugger. Jest uses exceptions internally for error handling, and the debugger was catching them.

If you’re seeing the same Cannot find module 'jest-sequencer-/package.json' error while debugging Jest, check your debugger breakpoint settings and make sure “Uncaught Exceptions” is the only one enabled. Disable “Raised Exceptions” or “All Exceptions”.

Marking this as solved. Let us know if anything else comes up.