Mike
banner
mootoday.com
Mike
@mootoday.com
Building https://pipestack.dev - Distributed workflows at scale.

25 years of helping businesses from 0 to 1. Now building my own product to do it all over again, solo.

Excellent developer experience leads to excellent customer experience.
Pinned
Mike @mootoday.com · Jun 22
Highly underrated technology in 2025: WebAssembly (Wasm) Components!

Instead of containers hundreds of megabytes in size, we're talking kilobytes.

Quick, resource efficient, completely sandboxed, and written in your language of choice that compiles to Wasm components.
🤫 Did you hear that just now?

That was me, celebrating the successful setup of NATS leaf nodes for pipestack.dev!

I need to push to prod, but soon™ you:
• bring your own code (not new)
• bring your own hardware (🆕)

This marks a major milestone, see the thread for why this is huge.
Distributed workflows at scale
Drag & drop to build your workflows. Upload your own code. Deploy to the edge, the cloud, or everywhere at once.
pipestack.dev
November 7, 2025 at 2:49 PM
If you use shadcn-svelte.com in your @svelte.dev app, here's a command to update all your components.

npx shadcn-svelte@latest add $(ls -d ./src/lib/components/ui/*/ | xargs -n1 basename)
November 6, 2025 at 2:39 PM
What kind of TUI (terminal user interface) would you use if it existed?
November 6, 2025 at 1:37 PM
I migrated pipestack.dev from Auth.js to Better Auth to reduce the default permissions the library asks for when people sign up with GitHub 💪.

Email is all I need and in line with what other web apps ask for too.

Thanks to a friend who pointed it out 🙏.
Distributed workflows at scale
Drag & drop to build your workflows. Upload your own code. Deploy to the edge, the cloud, or everywhere at once.
pipestack.dev
November 5, 2025 at 8:57 PM
A quick early morning quality of life improvement: proximity connect.

No customer complaints, but I've watched session recordings and it was painful to see people try to find the node handles 😥.

Dragging nodes also feels a lot more natural anyway.
No more "find the 10x10 pixel circle, drag, find another 10x10 pixel circle"!

With proximity connect, you simply grab a node, drag it close to another node you want to connect to and call it a day.
November 4, 2025 at 1:50 PM
"Instead of paternity leave, they ended my contract"

What's next?

1) pipestack.dev
2) Contract work to feed the family and keep our house

Over 20 years of experience, @svelte.dev since 2019, full-stack & CLIs with Typesript or Rust.

If I can help you, let me know.

mootoday.com/blog/instead...
Instead of paternity leave, they ended my contract - mootoday.com
When life gives you lemons, build your own lemon stand.
mootoday.com
November 3, 2025 at 1:12 PM
And if the browser doesn't provide said thing, check if your web framework does.

Read the docs, it's what separates an experienced developer from a know-it-all who doesn't know it all.
📝 Rather than shouldering the cost to design, build, optimize, and maintain your own implementation of a thing, consider leveraging the browser’s implementation of a thing which is free and (likely) optimized beyond anything you can do yourself.

blog.jim-nielsen.com/2025/browser...
Browser APIs: The Web’s Free SaaS
Writing about the big beautiful mess that is making things for the world wide web.
blog.jim-nielsen.com
November 3, 2025 at 12:33 PM
With public pipelines rolled out earlier today, it's now possible to access Pipestack without authentication!

Tech stack:
@svelte.dev, shadcn-svelte, @xyflow.com SvelteFlow (webapp)
• Rust (backend services)
@railway.com
@wasmcloud.com

Developed in @zed.dev.

pipestack.dev/demo/pipelin...
Pipestack | Builder
pipestack.dev
November 3, 2025 at 1:24 AM
Not a terribly exciting feature on its own, but crucial to building pipeline templates.

Step by step, I'm getting closer to shipping what Pipestack is all about:
• Bring your own code
• Bring your own nodes
• Run individual nodes (or entire pipelines) on your own hardware
Introducing public pipelines 🔓

With a flip of a switch, individual pipelines can be marked as public.

Public pipelines are accessible by anyone.

This marks the foundation for what we're going to work on next: templates.
November 2, 2025 at 10:35 PM
A 2 minute experiment with Google's Pomelli.

1. Enter pipestack.dev
2. Select a few things
3. Done
November 2, 2025 at 4:26 PM
In case I haven't shown enough @remult.dev beauty, here's another one.

This field is calculated based on the SQL expression and I can access it anywhere in my code (server and client). I can also use it to find and filter entities.
October 31, 2025 at 6:08 PM
Tomorrow's focus for @pipestack.dev: shareable pipelines.

It'll lay the foundation for templates, which will be the foundation for anyone to create and share nodes and entire pipelines.

That'll unlock two enterprise customers who want to share pipelines internally.
October 29, 2025 at 11:57 PM
TIL (and I can't believe it took me that long!) that @zed.dev has a Helix mode!

Oh... My... Goodness.

`gw` is by far the most efficient way I know to navigate in a file. Not yet supported in Zed, but at least I can now use one set of keybindings when I work in Zed vs Helix in the terminal.
October 29, 2025 at 11:02 PM
Another AI-assisted @svelte.dev UI development. There's a use case for AI in software development after all 😂.

Natural language input is a nice touch I haven't seen much used elsewhere. IMHO, it's such a convenient way to specify time.
"What happened two hours ago?"

"Something was off yesterday at 6pm"

Find logs for the exact time period you are interested in.

Support for natural language input is provided as well, e.g. "Yesterday at 6pm" and Pipestack knows what to do.
October 29, 2025 at 9:49 PM
Lots of reasons I've used @svelte.dev since 2019. "all you need to do is upgrade" is a big one.

It's been a theme in their developer experience and I'm here for it.
Combine it with forking and you can defy physics: svelte.dev/playground/7...

Out-of-order rendering uses static analysis (which we'll optimise further over time) and is fully automatic — all you need to do is upgrade
Out-of-order rendering with forking • Playground • Svelte
Web development for the rest of us
svelte.dev
October 28, 2025 at 9:40 PM
Not enough people understand that great developer experience leads to great customer experience.

Every friction, no matter how little, a developer deals with on a daily basis is one extra hurdle to take to experiment, ship quick bug fixes, release new features.

Invest time and money accordingly.
October 28, 2025 at 12:41 AM
Does anyone use OrbStack on Mac and has seen this?

It started to happen about a week ago and now happens once or twice a day.

To fix, a full laptop reboot is required.
October 27, 2025 at 1:58 PM
If your results don't look like that, I recommend you install @brave.com.

coveryourtracks.eff.org
October 25, 2025 at 8:43 PM
What he said.

IMHO, Biome isn't the way to go, never has been.

I tried to add it to a few projects and never succeeded in less than thirty minutes.

oxlint on the other hand just works, zero config to get started.
Yes! Let's set the record straight. Biome has very little support for Svelte. It's marketing gone overboard. It has no Svelte-specific rules that I'm aware of. I don't think it will ever be a competitive offering. My eyes are on oxlint, which is working towards being able to run eslint-plugin-svelte
> While we’ve done extensive work to handle many patterns, there are cases and framework-specific syntaxes that may not yet be fully supported (for example Svelte control-flow syntax, or Astro JSX-like syntax).

Sooo... Not full support then 😅
October 25, 2025 at 2:46 PM
If you develop software and write publicly available text (error messages, UI labels, etc.), here's a great spell checker!

github.com/blopker/code...
GitHub - blopker/codebook: Spell Checker for Code
Spell Checker for Code. Contribute to blopker/codebook development by creating an account on GitHub.
github.com
October 24, 2025 at 4:30 PM
15 minutes and voilà, we have a new log level selector.

90% of the work done by svelte0.com based on a screenshot I uploaded.

The remaining 10% with another LLM to change `
` elements to shadcn-svelte .
Why do people add CLAUDE markdown files to their source code when the industry collectively agreed on CONTRIBUTING files a decade ago?

A genius marketing move by the Claude team, but no other value beyond that.

It reminds me of "Sent from my iPhone" email signatures 😂.
October 22, 2025 at 8:31 PM
Reposted by Mike
Vitest 4 is out!

- Browser Mode is Stable
- Visual Regression Testing
- Improved Debugging
- Pool Stabilization
- New APIs
- Bug Fixes

Stay updated with our blog post:

vitest.dev/blog/vitest-4
Announcing Vitest 4.0
Vitest 4.0 Release Announcement
vitest.dev
October 22, 2025 at 3:43 PM
A project I came across just now hits all the buzzwords of 2025 😂.

"Blockchain execution layers for AI dApps"
October 21, 2025 at 10:50 PM