fix: Use --enable-source-maps flag in nodemon.json to show correct line number in stack trace #457
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.
Using a simple example like:
The current stack trace contains the line numbers of the transpile file but points to the ts file.
E.g. here it is line 12 but that's the
acceptMimes
lineUsing
--enable-source-maps
flags points to the correct line number (which is thethrow Error...
one).It also points e.g. to the
Hook.ts
file now instead of theHook.js
file but that shouldn't be an issue?If this is fine, eventually the migrate page shoudl reflect this in the
nodemon.json
example:https://tsed.dev/introduction/migrate-from-v7.html