Migrated from @Cloudflare to @Netlify.
If CF is going to keep pestering me about migrating from Pages to Workers, the least they could do is not make the process abysmally dogshit. Last drop was forcing me to download a .zip to delete my deployments.
https://t.co/I9X6xYptxB
Introducing shadcn/typeset.
You know how you render markdown and get back plain, unstyled HTML? Headings, paragraphs, lists, tables. So you style the elements one by one: font sizes, line heights, spacing.
You do it for your blog. Then you do it again for docs. Then again for the chat. Every time, you're fighting the same thing: sizing and spacing.
To fix this, we created typeset.css: one file that styles everything inside a typeset container. It lives in your project, so you can change it directly when you need to.
And we made it work beautifully with streaming markdown.
Starting today, we are making @base_ui the default component library in shadcn/ui.
First, a bit of history. When shadcn/ui launched in 2023, it was built on Radix. At the time, nothing else came close. Headless. Accessible. Composable.
Fast forward a few years and the team who built Radix are building something new: Base UI.
AWS AppSync Events really has got to be the unwanted child or something. Tons of stuff that should be in docs is in obscure blog posts in a "mobile" section of the website instead, and it's completely absent from AWS Labs or the new AWS Agent Toolkit - not even in skills.
@colmtuite Sounds like the right niche for riced up just-in-time UIs where apps just supply the API for your device/AI system a couple years down the line, maybe even using matching primitives
Can we not resort to this type of dogshit where you're so desperate to make me use vibecoding mode that you spam the most obnoxious UI highlights in an otherwise completely neutral interface @cursor_ai
@tannerlinsley No, `npx @tanstack/cli@latest create` doesn't prompt me for deployment adapter. Tested cmd, powershell and bash on Windows.
Name > Linter > Demo > add-ons > init
Bash also hangs after project name entry, which I can't reproduce with other CLIs like shadcn's init.
Surely I can't be the only person who REALLY dislikes the direction TanStack scaffolding has taken?
Builder was a concise & granular UI - became a unsectioned & biased AI-first interface. Also the CLI just has... no deployment adapter option?
Maybe I'm turning boomer-minded due to turning 30 in 2 days but all I see is obfuscation and removing control from user in favour of AI-first blackbox magic wand bullshit.
Esp. when manual integration notes have, historically, been behind latest methods that came with presets.
#1 win of Builder & CLI was explicit granularity for pre-formatted integrations without having to deal with mismatched/outdated subdocumentation for integration combos ++ up-to-date default foundation (ex., configs, new preset theme head script vs ScriptOnce in Provider)
@tinman2687@LSXYZ9 The hint about you being wrong is encased by the fact that you had to precise "it comes of as" & "I perceived it as" & "that's my opinion" in the span of a single tweet.