Skip to content
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

Closed
dustinbyrne opened this issue Jan 17, 2024 · 1 comment · Fixed by #97
Closed

Source paths are not resolved via source mappings #96

dustinbyrne opened this issue Jan 17, 2024 · 1 comment · Fixed by #97
Assignees
Labels
bug Something isn't working released

Comments

@dustinbyrne
Copy link
Contributor

dustinbyrne commented Jan 17, 2024

  • Using a Nest JS application written in TypeScript
  • Run via appmap-node nest start --watch
  • Request recording

Source code locations are resolving to .js files under the dist directory, instead of their TypeScript source.

@dustinbyrne dustinbyrne added the bug Something isn't working label Jan 17, 2024
@dividedmind dividedmind self-assigned this Jan 20, 2024
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)
@appland-release
Copy link

🎉 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
Labels
bug Something isn't working released
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants