modd

I wouldn't say "everyone" uses Air. I had never even heard of it, despite frequently developing in Go for close to a decade at this point. Modd is quite nice: https://github.com/cortesi/modd But, why couldn't you just use WSL? It is one of the main selling points of using Windows as a developer these days.

There's also modd[0] which allows for many file watch pattern -> command combos to easily be defined & run simultaneously from a modd.conf file. [0]https://github.com/cortesi/modd

If I'm understanding you correctly, then this combination of two tools from the same author will get you that: https://github.com/cortesi/modd https://github.com/cortesi/devd

I use a somewhat similar approach for Pirsch [0]. It's build so that I can run it locally, basically as a fully fledged staging environment. Databases run in Docker, everything else is started using modd [1]. This has proven to be a good setup for quick iterations and testing. I can quickly run all tests on my laptop (Go and TypeScript) and even import data from production to see if the statistics are correct for real data. Of course, there are some things that need to be mocked, like automated backups, but so far it turned out to work really well. You can find more on our blog [2] if you would like to know more. [0] https://pirsch.io [1] https://github.com/cortesi/modd [2] https://pirsch.io/blog/techstack/

I can recommend https://github.com/cortesi/modd, it seems like its not developed anymore though

This is by far the best tool for the job that I've found: https://github.com/cortesi/modd

> All I want from filesystem watcher is to track files by pattern and just re-run the command, however complex that may be to implement via OS interfaces. I've had good luck with modd: https://github.com/cortesi/modd/ I just tested exactly what you described, did not see any errors, and it ran my commands exactly the way I wanted.

A long time entr user, I recently switch to modd for flexible almost makefile like configurability, and watching/ignoring of multiple patterns to name a few convenient feature. https://github.com/cortesi/modd

- I use Browserify(1) because it allows me to use CommonJS(2) modules and bundle my JavaScript painlessly. - Beyond the pretty standard debowerify(3) and hintify(4) transforms I use babelify(5) to help me sprinkle fancy ES6 features here and there. - Node-based watchers and the npm client itself are all broken in many ways and very bad Unix citizens so I've stopped using npm for anything beyond actual package management and I will almost certainly replace the npm client with Yarn(6) very soon. The venerable make(7) or the much much younger but very dependable modd(8) are infinitely better than all that Node-based crap on _every_ front. - I use tape(9) for tests (works like node-tap(10) with a little fewer dependencies) but I _love_ the look of ospec(11) even if it's not TAP(12)-compliant. - Some JS libraries I've used recently: route-pars

A bunch of other excellent similar projects have been linked here, and here's mine - a general purpose tool that lets you put together flexible responses to file system change: https://github.com/cortesi/modd The use case here is deep and interesting, and I don't know of any tool that gets it 100% right. HN is often quick to grumble about reinventing the wheel, but where there is no clearly correct solution I think we should encourage experimentation. Modd is my opinionated take: it differs from other tools by trying to have a "proper" configuration language in which you can embed shell commands, by separating prep commands (that run and complete) and daemons (that run, but might need to be restarted on change), and by being completely agnostic about languages, test methodologies and other specificities of external tools.

Wu looks nice and simple. Did you know https://github.com/cortesi/modd when you started work on Wu?

I'm moving in a similar direction for similar reasons - but by shifting functionality out of the node ecosystem altogether. I recently released devd, a small, dev-focused HTTP server with build-in livereload which has taken the place of gulp livereload and node-based dev servers for many of my projects (https://github.com/cortesi/devd). I'm now working on the next step. It's not quite ready to be announced yet, but I'm cooking up modd, a similarly focused tool for monitoring the file system and responding to changes (https://github.com/cortesi/modd). Modd has already supplanted gulp entirely for many of my use cases, and has replaced supervisor and a bunch of other tools to boot. Many of the actions triggered by modd for front-end projects are precisely invocations of npm scripts as described in the article. A few more features (desktop n