Would you implement a simple protocol for the watch command?

Suggestion

Hi guys

I'm currently trying to get task-runners on board to create a protocol for watch-processes. The goal is that build-processes in watch mode do not automatically trigger a rebuild on file changes, but rather wait for the task-runner to tell them to do so. On the other hand, the watch-process should get a way to tell the task-runner when it's done and what the result is.

That's pretty much it, and it would be a very simple protocol.

Since TypeScript is the prime use case I have in mind for this, I thought I should ask you guys what you think about the idea. If such a protocol existed, would you implement it?

I'm trying to get the discussion started here: https://github.com/VanCoding/task-graph-protocol/issues/3
And here's a link to my example protocol and implementation, which also already has an implementation for tsc: https://github.com/VanCoding/task-graph-protocol

🔍 Search Terms

watch process

Related issues #33388 #20258 #19584 #41611 #42838

✅ Viability Checklist

My suggestion meets these guidelines:

• This wouldn't be a breaking change in existing TypeScript/JavaScript code
• This wouldn't change the runtime behavior of existing JavaScript code
• This could be implemented without emitting different JS based on the types of the expressions
• This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.)
• This feature would agree with the rest of TypeScript's Design Goals.

Das Issue nennt keine TypeScript-Repositorydateien, Tests oder Einstiegspunkte. Beginne mit der Durchsicht der verknüpften task-graph-protocol-Diskussion und Beispielimplementierung und untersuche anschließend die verwandten Issues #33388, #20258, #19584, #41611 und #42838. Für den Abschluss wären ein akzeptiertes Protokolldesign und ein bestätigter Implementierungsumfang für den watch command erforderlich.