--watch behaves strangely about deno

[lucacasonato]

When specifying --watch, the script program will restart if any of the files in the module graph (so the entrypoint, or any file imports from it or any of it's dependencies) change.

You can pass additional files or folder to --watch as paths relative to your cwd. When passing multiple paths, separate them with ,. This is also explained in the help text.

      --watch[=<FILES>...]
          Watch for file changes and restart process automatically.
          Local files from entry point module graph are watched by default.
          Additional paths might be watched by passing them as arguments to this flag.

Finally, you can exclude files from being watched, by specifying a --watch-exclude flag:

      --watch-exclude[=<FILES>...]
          Exclude provided files/patterns from watch mode

The behaviour where non existant paths are not an error is expected and desired - we want to allow you to watch a directory or folder that does not exist yet, that may only be created by the script itself during execution.

[bkerin]

You're right the default is specified. I'd phrase it differently though since it's a little unusual to have an option with an argument also have a global effect. The use of commas isn't documented as far as I can tell though, and neither is the pattern format referred to. Maybe it could be rewritten like this:

 --watch={=<FILE_PATTERNS>...]
    Watch for file changes and restart process automatically.
    When this option appears local files from entry point module graph are watched by default.  If an argument is provided to this
    option it give a comma-separated list of ???-style file patterns that will also be watched.

I still don't know what file patterns are supported. It doesn't seem be be shell-style globs (e.g. *.perl).