just

I've found the script runner "just" to be worth using. https://github.com/casey/just just (at a glance) is like a Makefile, but with some nice UX improvements that make it worth using. e.g. with `just --choose`, it runs fzf against the targets.

Throwing my hat in the ring for Justfile. It's basically a streamlined make. https://github.com/casey/just Where it really shines are in places like monorepos where you may have many inter-related setup scripts, build commands or helper utilities. You define all of your commands in one file (or multiple if you want a hierarchy) and can run commands from any subdirectory. eg. You have a monorepo with a web server, and also a react-native app in separate directories, you can call `just build-app` in the web directory, or call just `start-server` when your terminal's current directory is 7 diretories deep in the mobile directory. The amount of time I have saved cd'ing around has honestly been amazing. It's worth it's weight in gold, especially on large projects.

Aaarg, I hate to always be the person that points out "naming issues", but there is already a pretty popular command runner with the name just: https://github.com/casey/just

+1 for Justfiles[1]! They're a much saner alternative to makefiles with great shell support [1] https://github.com/casey/just

Hey HN, I built randomneo.city since people didn't like my comment on the randomgeo.city post[0]. Clearly I don't take downvotes well. That said, the code is powered by SvelteKit, SQLite and open source: https://gitlab.com/mrman/randomneocity I have to say, I'm really starting to like building everything with SvelteKit -- I'm a huge 3-tier architecture fan, and it just doesn't make sense these days to add an API repo for most small projects now. Node + TS + SvelteKit does most (to be fair, so would Nuxt or Next). It's been a fantastically productive stack for me. Things I still need to do: - Add automatic scraping of neocities' sites so the site can stay up to date - Filter out sites which aren't done (they all have the same text) - Add chat/social features (???) This was also a great chance to try out Just[1] which strives to replace mak

I think the `.RECIPEPREFIX = >` bit triggered a lot of people here in the comments, and I agree. That would make drafting newlines a huge pain in any editor. Just enable "Show Whitespace" in your editor if you want this. That said, I'm more concerned about the guidance to not use .PHONY and instead do this: # Tests - re-ran if any file under src has been changed since tmp/.tests-passed.sentinel was last touched tmp/.tests-passed.sentinel: $(shell find src -type f) > mkdir -p $(@D) > node run test > touch $@ The author is right, that does use make in a more more idiomatic way by relying on a real file, but I see 2 major problems: * That's a lot of logic for something that should just be super simple. * When I say `make test` I want it to run the tests. I don't care if they've passed before and the files haven't change

Reminds me of just, sake or rucksack. https://github.com/casey/just https://github.com/alajmo/sake https://github.com/acritelli/rucksack

True, that's where Make shines. Though given the popularity of so many Make alternatives (the strictly subset of command runner variety, like just[1]) who keep its syntax but not this mechanism, I wonder if for command runner unnecessarily re-running dependencies is really a big deal. Because quite often the tasks are simple and idempotent anyway, and then it's a bit of a hassle to artificially back the target by a dummy file in Make (which your example doesn't do here e.g.). [1] https://github.com/casey/just

For a task runner I really like just and its Justfile format: https://github.com/casey/just It is heavily inspired by make but doesn't focus on the DAG stuff (but does support tasks and dependencies). Crucially it has a much better user experience for listing and documenting tasks--just comment your tasks and it will build a nice list of them in the CLI. It also supports passing CLI parameters to task invocations so you can build simple CLI tools with it too (no need to clutter your repo with little one-off CLI tools written in a myriad of different languages). If most of your make usage is a bunch of .PHONY nonsense and tricks to make it so developers can run a simple command to get going, check out just. You will find it's not difficult to immediately switch over to its task format.

I use "just" for this purpose, and I'm very happy with it: https://github.com/casey/just

Also related & interesting: - https://frippery.org/make/ (inspired this post -- HN: https://news.ycombinator.com/item?id=32300356) - https://github.com/casey/just (Make with less footguns, written in Rust) [EDIT] A side-note -- I personally use Make with just all stacks I create with (front/back/infra/etc). I think it's quite undervalued but maybe because I've never dealt with an industrial-strength terrible Makefile setup that would turn me off to it.

I really liked the Just README recently: https://github.com/casey/just/blob/master/README.md

I thoroughly enjoyed the README for the just tool the other day - very thorough, answered all of my questions, fun to read: https://github.com/casey/just/blob/master/README.md