-
Notifications
You must be signed in to change notification settings - Fork 12.8k
///references should support resolving environment variables #4615
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
Comments
one thing to note, tsconfig.json does not support environment variables either. |
+1 for parsing environment variables in (at least) tsconfig.json. Build systems that want to use this file rely on being able to use variables for things like output directories. |
+1 |
2 similar comments
+1 |
+1 |
+1 |
We're at ~9 upvotes after five years of being opened and this opens up a big can of worms for things like cloud build systems; with other means to have file inclusion we've added in the meantime, I don't think this one meets the bar for implementation. |
For example, instead of using
/// <reference path="../../../myCustomPathWhichMightNotWorkOnMyCoWorkersComputer/library.d.ts" />
I’d like to use either
/// <reference path="$(MY_PARTNER_TEAM_LIB)/library.d.ts" />
Or
/// <reference path="%MY_PARTNER_TEAM_LIB%/library.d.ts" />
The text was updated successfully, but these errors were encountered: