2 hours ago · 9 min read1811 words · Tech · hide · 0 comments

neorepl 0.4 came out last week, and since I never got around to writing about 0.2 and 0.3, it feels like a good moment to look back at what happened since the original announcement. Three releases in two weeks, and neorepl now has most of what I listed under “What’s next” back then - a test runner, a full-screen inspector and stacktrace browser, an MCP server and a skill for coding agents - plus a few things that weren’t on the list at all, like tracing and peeking into your coding agent’s REPL session. Running tests ,test in the REPL, or neorepl test in your shell, runs the tests in the namespaces you name, the tests you name or, without either, the whole project’s. Failures come with their file and line, and errors with a stack trace that stops at the test that hit them, instead of wandering off into clojure.test’s guts. ,retest (neorepl retest) reruns only what didn’t pass, which is exactly what you want while you’re fixing things. As usual, the server does the heavy lifting.…

No comments yet. Log in to reply on the Fediverse. Comments will appear here.