Support for --trace-warnings option?

[bitliner]

I would need to run ts-node and print stack trace for unhandled promise exceptions.

How to pass an option --trace-warnings?

[blakeembrey]

Feel free to submit a PR. It would need to be added to

ts-node/src/bin.ts

Line 19 in c57ded2

const knownFlags = v8flags.concat([

. This code may be refactored before 4.0 though because of #459 and would also result in resolving this.

[stelcheck]

@bitliner made a PR to add the flag, see #476

[blakeembrey]

@stelcheck If you can split out this issue with the other one, I can merge one before the other. Thanks!

[stelcheck]

Done.

[kateile]

@stelcheck how to use it?
I tried adding script in package.json as
"dev": "ts-node --trace-warnings src/server.tsx",
but i get error when run it

[stelcheck]

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.

[Elyx0]

Doesn't work @stelcheck still getting the error on --trace-warnings

[Elyx0]

node  --trace-warnings -r ts-node/register -r tsconfig-paths/register ./src/index.ts

For future reference, this worked

[LeonardoRick]

should I be able to run ts-node --trace-warnings in 2020?

[cspotcode]

In 2020 specifically, you're supposed to do this: #465 (comment)

If you find yourself in 2019, you might need to do something else.

[Psychosynthesis]

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?