Unable to debug with --watch

[supersonicclay]

Type of issue

Bug

Description

Unable to debug with fusion test --watch --debug

This works:

JEST_ENV=dev node --inspect ./node_modules/.bin/jest --config=./node_modules/fusion-cli/build/jest/jest-config.js --watch --runInBand --no-cache

Neither of these works:

./node_modules/.bin/fusion test --watch --debug
./node_modules/.bin/fusion test --watch --debug --runInBand --no-cache

It hits the breakpoint in node_modules/jest/bin/jest.js, but not in my actual test. I'm using latest fusion-* versions.

Your environment

• fusion-cli version: 1.15.1

• Node.js version (node --version): 8.12.0

• npm version (npm --version): 6.4.1

• Operating System: OSX

[KevinGrandon]

Re-opening since we are able to reproduce with an internal app, and using VS Code. Potentially related to source maps?

[KevinGrandon]

I believe this case was due to a top-level jest dependency declaration, we shouldn't have those.

[supersonicclay]

@KevinGrandon I removed jest from top level devDependencies and it still doesn't hit breakpoints in my tests with VS Code.

[KevinGrandon]

Summary of current issues:

• Breakpoints not working in VSCode.
• Debugger statements "sometimes" work, depending on line.
• File tree is missing in the chrome inspector.

Current hunch is that there is a sourcemap or configuration mismatch.

Note: These manifest when opening upt he "dedicated DevTools for Node" as well.

[KevinGrandon]

Potentially useful resource: https://stackoverflow.com/questions/50765353/visual-studio-code-breakpoint-appearing-in-wrong-place