Luca Bertelli

There was no TanStack Router for TypeScript CLIs. So I built parsh. Type-safe end to end. File-based commands. Typo a positional param, the compiler tells you which one. Parent options autocomplete in nested handlers. And more. 90s of the type system catching every drift:

Super useful feature! I don't get why other messaging apps still don't have it, especially on @SlackHQ where agreeing on a datetime with a remote coworker is so frequent and painful: "wait but are you in summer time?" Is should be as simple as @ tagging a datetime on @NotionHQ

@jarredsumner @thdxr How about the opposite instead? Making the Bun crates available

@thdxr We will continue to have our own. Bun’s is faster than everything else I’ve seen and also has the features and cohesive DX we want.

so should bun even have its own parsers and bundler anymore or should it just build with the void0 crates

@GiulioVaccari Hahaha really cool! I'm bad at selfies, so this may help

We went to a robotics hackathon and wanted to do something with cameras. We derailed and made a thing to take selfies with London TFL cameras. No prize but we got some great shots of elephant & castle: londonselfiecam-virid.vercel.app

The more you prevent at compile time, the better. Especially if it's an AI writing it. That's why I built Parsh, the TanStack Router for TypeScript CLIs. It won't even compile if you access an option not in the command's ancestry. Other CLI frameworks let you ship that bug

@NiklausFuller There's been a similar discussion going on here, interesting comments: reddit.com/r/ClaudeAI/com…

Claude Code and Claude should share chats. Why can’t I reference a Claude code session within regular Claude? Headache.

You'll need an agentic Slack more than an agentic IDE

Hey @jarredsumner, why isn't Bun the default runtime in bun run and bunx? And if I want to run on Node.js instead, I can specify --node. Feels more ergonomic

@1weiho Cool! I used @Slidevjs which makes you write Markdown, but I guess using React makes it more flexible and powerful

Introducing open-slide - The slide framework built for agents. Prompt your agent, get a polished deck. $ npx @⁠open-slide/cli init 👇

New in parsh: atomic, type-safe command testing. Run any lifecycle hook in isolation. Options, params and context are end-to-end inferred, like anything else in parsh.

Any other suggestions?

Make the gitignored files appear more dimmed: "theme_overrides": { "VSCode Dark Modern": { "ignored": "#666", "version_control.ignored": "#666" } }

Switching from VS Code to @zeddotdev. These are the settings I changed to feel at home:

Start building amazing CLIs: github.com/ilbertt/parsh

There was no TanStack Router for TypeScript CLIs. So I built parsh. Type-safe end to end. File-based commands. Typo a positional param, the compiler tells you which one. Parent options autocomplete in nested handlers. And more. 90s of the type system catching every drift:

@saen_dev Each file in the commands folder is automatically picked up as a (sub)command based on the folder structure. src/commands/deploy/[name].ts -> mycli deploy <name> With the possibility to define alias commands while maintaining type-safety

@ilbert_luca TypeScript CLI tooling is still way behind what Python has with click and typer. A proper router pattern for CLI commands is exactly what's missing, curious how you're handling subcommand composition.

Been building parsh, the TanStack Router for TypeScript CLIs