elm-watch VS denon

There was a post here about elm-watch, which is amazing. But setting that aside, if you have a frontend development workflow where you want to have more than 1 thing running at once, you should check out [run-pty](https://github.com/lydell/run-pty). It's made by the same guy who wrote elm-watch and if you look at the [example](https://github.com/lydell/elm-watch/blob/main/example/run-pty-dev.json) for elm-watch you'll see how elm-watch and run-pty can be used together to great effect. And if you look at the run-pty [demo](https://github.com/lydell/run-pty/tree/main/demo) you'll see how it can be used sans Elm as well.

{ "$schema": "https://deno.land/x/[email protected]/schema.json", "scripts": { "start": { "cmd": "deno run main.js", "desc": "start server", "tsconfig": "tsconfig.json", "importmap": "importmap.json", "allow": [ "net", ] } } }

Hey, I found an an issue in the denon repo, but it looks like there aren't any fixes for Deno v1.7.1 right now. However, for the time being, I advise you to add the --watch flag to Deno run and it will also rerun your app on any changes.