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
It looks like the --watch options is still a boolean flag though. You can verify this by passing a file to --watch which is not part of the entry point module graph and then edit that file. You'll see that only the entry point and its dependencies are watched. The example in the issue you linked is probably working because the watched .ts files are already part of the module graph (and the value of the boolean flag is ignored I guess?).
I guess another option would be to leverage https://deno.land/x/[email protected] . I wonder if I could do that in user space even. In this case I would have to trigger whatever Deno's watch is triggering right now and if we're lucky there's a programmatic hook for that.
It would be good to support patterns for
watch
. I.e.scripts.json
Based on denoland/deno#2401 (comment) Deno supports
deno run --watch=./**/*.ts,./**/*.tsx server.ts
kind of syntax.Looking at the code, the command builder would have to be extended to support strings beyond booleans (
case DenoOptions.watch: {
in code).The text was updated successfully, but these errors were encountered: