enabling source maps #2845
mschmitz-personal
started this conversation in
Help Wanted
Replies: 1 comment
-
Hi everyone, I am using the default tsc config as it comes with nitro:
This is pretty mch as it comes with Nitro. I added the sourceMap as you can see. If I do as "tsc --build" now then I am getting a lot of errors related to the tilede "~" in import statements and these statements not finding files.
Is there a way to use "tsc --build" to rebuild the whole tree and getting an overall syntax check? If this is not suitable in nitro, how do you achieve such? Regards Markus |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi everyone,
I just started to dip my feet into nitro (on windows) and I am facing, what must be a beginners problem.
When my backend throws an exception, I get a stacktrace (both on the console as well as ion the response), but that stack trace references the compiled JS files. Example:
I assume that somehow the source maps are not enabled, not generated or not used. I enabled them both in the tsconfig:
and in the nitro config:
What am I missing here? How can nitro be configured to make use of the source maps, so that the stack trace has more value?
Also how can I trigger a full compile, so that any inconsistencies as a consequence of global refactoring show up? Currently they show up nicely in VS Code, if I open the problematic file only. The normal full build runs without errors, even though the code clearly has issues and also flags them in the IDE. I know that must be quite a noob question also ...
Thanks for your help
Markus
Beta Was this translation helpful? Give feedback.
All reactions