-
-
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
[docs] Usage with VS Code Debugger. #590
Conversation
Hey ! I bumped into the problem referenced here : TypeStrong#565 I added this for future me and others :) Cheers !
This is true for pretty much any usage of |
@blakeembrey Yeah, that's a good point ! I changed the wording to be less specific to VS Code and replaced with npm -D but please feel free to dismiss the PR if you feel it adds confusion. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would make it clearer that the "in your project" option is for when you want to use an IDE.
Installing ts-node and typescript globally works fine for people not using any IDE at all, I'm guessing that's why this is the common example. Part of making open source documentation good is keeping it as agnostic as possible, so that it's easier for every reader to digest.
Alternatively, in the readme, there is also a section on using ts-node in Visual Studio Code specifically, so perhaps a note could be added there saying "you must install ts-node and typescript locally".
Hey !
I bumped into the problem referenced here : #565
I added this for future me and others :)
Cheers !