You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The built-in ts.syswatchFile and watchDirectory methods bind process.cwd() at the moment of instantiation. This inhibits the ability of heft-typescript-plugin to change working directories between compilations (mostly relevant if running as a service).
Repro steps
Not reproducible via CLI. Happens when attempting to leverage Heft as an API to conserve system resources.
The watchFile and watchDirectory methods need to be rebound to reflect the custom getCurrentDirectory() call. Might be worth reaching out to TypeScript to make the method that creates ts.sys publicly callable.
Standard questions
Please answer these questions to help us investigate your issue more quickly:
Question
Answer
@rushstack/heft-typescript-plugin version?
0.4.0
Operating system?
Linux
Would you consider contributing a PR?
Yes
Node.js version (node -v)?
v18.19.1
The text was updated successfully, but these errors were encountered:
Summary
The built-in
ts.sys
watchFile
andwatchDirectory
methods bindprocess.cwd()
at the moment of instantiation. This inhibits the ability ofheft-typescript-plugin
to change working directories between compilations (mostly relevant if running as a service).Repro steps
Not reproducible via CLI. Happens when attempting to leverage Heft as an API to conserve system resources.
Details
See comment here:
https://github.com/microsoft/rushstack/blob/8fe0ea8f861a1cecd8b964bcdabc610f2a5574e3/heft-plugins/heft-typescript-plugin/src/TypeScriptBuilder.ts#L313C1-L313C58
The
watchFile
andwatchDirectory
methods need to be rebound to reflect the customgetCurrentDirectory()
call. Might be worth reaching out to TypeScript to make the method that creatests.sys
publicly callable.Standard questions
Please answer these questions to help us investigate your issue more quickly:
@rushstack/heft-typescript-plugin
version?node -v
)?The text was updated successfully, but these errors were encountered: