-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Source paths are not resolved via source mappings #96
Comments
dividedmind
added a commit
that referenced
this issue
Jan 21, 2024
dividedmind
added a commit
that referenced
this issue
Jan 21, 2024
dividedmind
added a commit
that referenced
this issue
Jan 22, 2024
dividedmind
added a commit
that referenced
this issue
Jan 24, 2024
dividedmind
added a commit
that referenced
this issue
Jan 24, 2024
appland-release
pushed a commit
that referenced
this issue
Jan 24, 2024
## [2.14.1](v2.14.0...v2.14.1) (2024-01-24) ### Bug Fixes * Handle external source maps ([01d9a09](01d9a09)), closes [#96](#96)
🎉 This issue has been resolved in version 2.14.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
appmap-node nest start --watch
Source code locations are resolving to
.js
files under thedist
directory, instead of their TypeScript source.The text was updated successfully, but these errors were encountered: