Support Typescript source map resolution #30
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
added 5 commits
January 2, 2020 17:07
than tslint so committing the prettier version
added 4 commits
January 3, 2020 22:22
coverage requirements
up in local runs
variable is not initialized
|
I tried to raise code coverage to pass the tests by either writing .map files or using |
permanently so CI tests can hopefully execute
|
I've added a static .map file to the |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Hi,
I've created this patch to support source map resolution for Nest TypeScript applications. It is a somewhat simplistic solution as it does not read the source map tag in the compiled JS files. It assumes the source map file is right beside the compiled JS file. This is what
nest startdoes by default.Let me know if there are any issues with this PR, I'm happy to work on it.