Microsoft doesn’t use this kind of wording unless it’s really really bad. Like, SHTF kinda bad.
“Aggressively pursuing all pathways…we’ve paused all new deployments.”
That’s a panic button I’ve never seen them hit before.
“The elevated load isn’t driven by an increase in traffic, but by a number of servers being UNEXPECTEDLY UNAVAILABLE.”
IE: Server farms. Racks and racks of servers. NOT RESPONDING. At all. Failing health checks.
Whew doggie!
Upgraded https://t.co/x6hbCT78LH from SolidStart v1 to v2 (Nitro v3 + Vite 8) on Cloudflare Workers and Pages. It’s not a version bump, it’s a tooling swap: Vinxi is gone. #SolidJS#vite
The best part of the migration: build times 🚀
12/
Result: auth work, file previews, emails and all five purge crons run on v2. Longer than “swap a dependency”, but every error was findable. Happy to share more detail if it’s useful. #SolidJS#SolidStart
1/
Upgraded Birchly from SolidStart v1 to v2 (Nitro v3 + Vite 8) on Cloudflare Workers and Pages. It’s not a version bump, it’s a tooling swap: Vinxi is gone. Here’s what broke and what to check before you try it 🧵 #SolidJS#SolidStart
11/
Checklist: Node 24+, router bump, drop the h3 override, process.env in client code, context.cloudflare reads, client-only libs leaking into server bundles, task folder and imports, cron list, lockfile vs the build’s npm, and run each scheduled task once.
@ray_kovalev I hear you. The step is also groundwork for client accounts (orgs inviting their clients), and since that's not built yet it just feels like an extra step for now. Performance fix is next on my list, will post about it here when it ships.
Shipped Docs in Birchly this week. It’s not final (table colors and more embed types are still on the list), but you can already write, share and publish docs as web pages. #buildinpublic#solidjs#saas
I set a goal of 10 early users for my SaaS. I'm at 8.
Early access gave me a long list of bugs I'd never have found and requests that showed me what to build next.
Biggest lesson: put a feedback button inside the app from day one. #SaaS#BuildInPublic
@julienlevallois@YouTube How I triage:
- Vision fit first. Scope creep is a no, no matter who's asking.
- Volume second. Demand shows up before pricing.
- Paying third. Tiebreaker, not override.
- Effort. Ships this week beats next month.
- And the why. Two contradictory requests are sometimes the same.