-
-
Notifications
You must be signed in to change notification settings - Fork 536
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
Support for --trace-warnings option? #465
Comments
This will remap all `TS_NODE_` environment to `NODE_` environment variables for the child process being spawned. Fixes TypeStrong#465 TypeStrong#471
@stelcheck If you can split out this issue with the other one, I can merge one before the other. Thanks! |
Done. |
@stelcheck how to use it? |
Have a look at https://medium.com/the-node-js-collection/node-options-has-landed-in-8-x-5fba57af703d - this should allow you to define Node.JS flags and options through environment variables. |
Doesn't work @stelcheck still getting the error on --trace-warnings |
For future reference, this worked |
should I be able to run |
In 2020 specifically, you're supposed to do this: #465 (comment) If you find yourself in 2019, you might need to do something else. |
It work, but looks awful. Why can't just add a parameter to the ts-node section in the config? |
@Psychosynthesis This has been discussed many times before, but the short of it is: not possible because we don't spawn a subprocess. Doing so adds extra complexity for users and maintainers, and incurs a performance penalty. |
I use this and it works 🤔 |
@LeanKhan Doesn't work. When I run it, I get:
|
@benallfree I was using a previous version of ts-node: |
for anyone who wants to run ts-node and print stack trace for unhandled promise exceptions. node --loader ts-node/esm --trace-warnings exemple/index.ts make sure to have ts-node installed as a dev dependency. |
I still get error with this --trace-warnings flag. Has no one fixed it yet. |
I would need to run ts-node and print stack trace for unhandled promise exceptions.
How to pass an option
--trace-warnings
?The text was updated successfully, but these errors were encountered: