feat(debug): Dynamic debug path resolution for TypeScript/Jest #61
Conversation
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
…results When the BSP server returns source items, filter out invalid paths that should not be treated as test sources: - node_modules paths (dependencies, not actual test files) - bazel-out paths (compiled JS files, not source TS files) This ensures that jest_test targets with complex dependency structures are correctly handled, and the source inference fallback is triggered when needed. Added TypeScriptLanguageTools.isValidTestSource() static method to centralize the validation logic.
- Add BazelInfoService to query execution_root, output_base, and platform - Add TypeScriptLanguageTools.constructDebugRemoteRoot() to build runfiles path - Fix race condition: await prepareDebugInfo() before test execution - Dynamically inject localRoot/remoteRoot into debug config at runtime This eliminates the need for manual sourceMapPathOverrides configuration in launch.json. The debugger now automatically resolves paths based on the Bazel execution environment and target being debugged.
Handle targets in nested packages (e.g., @//src/path/to/pkg:target) by extracting and including the package path in the runfiles directory. Previously only root package targets (@//:target) worked correctly.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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
Implements dynamic debug path resolution for TypeScript/Jest tests. The debugger now automatically resolves
localRoot/remoteRootbased on the Bazel execution environment, eliminating the need for manualsourceMapPathOverridesconfiguration.Changes
BazelInfoServiceto query Bazel execution_root, output_base, and platformTypeScriptLanguageTools.constructDebugRemoteRoot()to build runfiles path dynamicallyprepareDebugInfo()before test execution@//src/path/to/pkg:target)Testing