On linux or editor with canUseEvents to prefer immediate directory if its not in root or node_modules#58866
Conversation
|
Looks like you're introducing a change to the public API surface area. If this includes breaking changes, please document them on our wiki's API Breaking Changes page. Also, please make sure @DanielRosenwasser and @RyanCavanaugh are aware of the changes, just as a heads up. |
|
cc: @dmichon-msft |
|
@typescript-bot pack this |
|
Hey @sheetalkamat, I've packed this into an installable tgz. You can install it for testing by referencing it in your and then running There is also a playground for this build and an npm module you can use via |
|
I'm working on pulling this down to test in my environment. I'll note that I find it useful to also have a toggle to disable watching any path that contains a |
|
Ah, right, I can't test this directly in my target repository, need to experiment with consuming it from heft-typescript-plugin and passing the necessary config option first. That'll take a bit longer to set up. |
560ac16 to
a820f56
Compare
|
Happy to see this, but it looks like I need to do some work to be compatible with the various changes that shipped in TypeScript 5.5 before I'll be able to test it E2E. |
a820f56 to
827866a
Compare
827866a to
651bfe2
Compare
|
Ran a experiment with watching Users who dont want to watch |
|
@typescript-bot test it |
|
Hey @sheetalkamat, the results of running the DT tests are ready. Everything looks the same! |
|
@sheetalkamat Here are the results of running the user tests with tsc comparing Everything looks good! |
|
@sheetalkamat Here they are:
tscComparison Report - baseline..pr
System info unknown
Hosts
Scenarios
Developer Information: |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
@sheetalkamat Here are the results of running the top 400 repos with tsc comparing Everything looks good! |
| interface ServerHost extends System { | ||
| watchFile(path: string, callback: FileWatcherCallback, pollingInterval?: number, options?: WatchOptions): FileWatcher; | ||
| watchDirectory(path: string, callback: DirectoryWatcherCallback, recursive?: boolean, options?: WatchOptions): FileWatcher; | ||
| preferNonRecursiveWatch?: boolean; |
There was a problem hiding this comment.
Is the intent that downstream users configure this? Do we need to wait for David to check that this helps?
There was a problem hiding this comment.
I was not sure whether to leave this public on ServerHost or not but TscWatch yes because i think last i checked david was using the API to patch tsc watch.
I am looking to get this in early and revert or reiterate sooner than later as we dont get more feedback without this being in nightly esp since this depends on OS and vscode setting to use their watchers
There was a problem hiding this comment.
i can make these internal on tsc-watch and tsserver internal and make them public in next PR if they are needed if that approach is better
There was a problem hiding this comment.
Understood; just checking; I think you have more context than me on this.
Experiment with what to watch with
preferNonRecursiveWatchoption on the hostHelps with #58319