-
-
Notifications
You must be signed in to change notification settings - Fork 530
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
Add tsconfig-paths
to documentation
#704
Comments
It is in the README under the |
@blakeembrey do you think this is adequately covered by this page? https://typestrong.org/ts-node/docs/paths |
@cspotcode it's informative... but it should probably contain some samples of common scenarios, known bugs and links to the issues about this. |
@rayfoss how about this as a plan forward? I think it strikes a balance between improving the docs, saving the team's limited time resources, and giving users agency to help each other. It effectively solves the core problem which is: "make this work for users"
If that plan sounds good, I can mark this ticket as "help wanted" and allow the community to tackle all of those tasks. |
I learned about tsconfig-paths in #138.
Path mappings are very useful, so using
tsconfig-paths
is often a must have for me when usingts-node
.I think it would be helpful to list of useful modules like tsconfig-paths in the README.md. (Similar to recommendations made for Watching and Restarting.)
EDIT from @cspotcode: marked this ticket as "help wanted" with a list of tasks here: #704 (comment)
The text was updated successfully, but these errors were encountered: