-
Notifications
You must be signed in to change notification settings - Fork 74
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 tsc --p option? (path to project) #168
Comments
Try something like this:
|
Oh that's great! That seems to be working, thank you! |
Documented by @cartant Thanks again ! 👍 🌹 |
@basarat Actually, it seems that I've missed the author's intentions re:
I'll submit another PR later to tidy up the |
@basarat Unfortunately, my change to expand the short-name, command-line options resulted in the target defaulting to It's a little embarrassing, that the first release for which I've been responsible is broken. Clearly, I'll have to have a closer look at the testing environment the author has set up, so that I can add some tests that cover additions like the one I've just made. |
I'd like to be able to supply the path to the tsconfig.json file, but tsify doesn't seem to pass this through to tsc.
Eg:
So it won't pick up any of the options in tsconfig.json, meaning I have to re-add them to the command line. This gets especially bad when you have a lot of typings files as you can't include them with a wildcard. Eg:
Is there a way to set the path to tsconfig.json?
The text was updated successfully, but these errors were encountered: