-
-
Notifications
You must be signed in to change notification settings - Fork 431
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
Initial implementation of trace for traceResolution in #691 #721
Conversation
That's fine - talk to me how this would be used / what output you expect to see when you are using it. Let's see if I can help you. |
My guess is we can clone an existing test ( Then:
|
Sooo, I did it .. good news is your instructions worked like a charm. Bad news, the stdout isn't stored in the expected output. Also, the full path to the files is in the logs, which makes them un-reproducible. What can I do to make it write the output to The Full output I get is the following : Expected output redirected to stdout
|
Oh wow. Yeah - that makes sense. Bottom line, this is a 1 line change - it doesn't break existing tests and it adds functionality. Merged. |
Oh, thanks :) That was fast |
Released with v3.5.0: https://github.com/TypeStrong/ts-loader/releases/tag/v3.5.0 |
Hi,
sorry for the long time between the initial discussion and the pull request. I tried to do the first implementation for issue #691
I tried to write a test but could not. When running them it gets stuck at the first test: