Steven ⬢ retweeted
New from Vercel Labs: tsc-ts
TypeScript was written in TypeScript
Then rewritten in Go
We ported it back to TypeScript
Compiled it with scriptc
And it's 2-4x faster than tsgo
I ask “where do you live?” and then if the conversation takes us there, “have you always lived there, is that where you’re from?”.
I find most people actually don’t currently live where they grew up so it’s not like a one sided question.
The best part is it works with both git CLI but it also works when viewing history on GitHub.com
Steven ⬢ retweeted
Unlimited Vercel Blob stores on every plan.
Starting today there's no limit on how many stores you can have. A store per customer, project, or job now works at any scale.
vercel.com/changelog/unlimit…
Steven ⬢ retweeted
We collaborated with @HacktronAI to reproduce the libheif vulnerability in Next.js and responsibly disclose it to the maintainer.
Learn about the dependency chain and fix ↓
vercel.com/blog/reproducing-…
Steven ⬢ retweeted
Jev by @typesafeai is free on Vercel AI Gateway until Sept 25.
Build with the fastest adopted model on the Gateway at no cost.
vercel.com/ai-gateway/models…
xitter.cf/vercel/status/21010773…
Jev was adopted faster than any other model in AI Gateway history.
In the first day, @typesafeai reached ~13% of teams, 2x the GPT-5.6 family and 6x Fable 5.1.
Wild that the vercel-labs org is already number 54 for most stars on github (currently 220k ⭐)
gitstar-ranking.com/organiza…
Introducing Vercel Labs
Tools for devs in the AI era
agent-browser, skills, json-render, deepsec, fx, just-bash, portless, vgpu and more
We experiment in public: ship early, learn from feedback, and keep working on what people find useful
We've been shipping under the Labs name for a while. Now, Labs is an official team at Vercel focused on exploring new capabilities and primitives that change what developers and agents can do.
Here's what to expect:
→ Labs products: maintained, supported, built to be relied on
→ Active experiments: moves fast, expect rough edges and breaking changes
→ Past experiments: ideas that become new projects, make it into existing products, or teach us what to build next
vercel.com/labs?experiment-i…
This is why I still buy music.
Streaming is nice to find something new but you won't actually care about something unless you buy it.
Someone explain this.
I pay for Netflix, HBO, Disney+, Prime. Unlimited movies. I never watch anything.
I buy one movie for $19 on Apple TV. I watch that.
Every company should generate a CLI from their API - it should just be another way to interact with the API but we should stop spending so much effort on the CLI and instead improve the API 👍
The best part about hosting on Vercel - any performance improvement to the CDN makes websites faster for everyone ✨
Don't forget to redeploy 🚀
The Vercel CDN makes over 80 million routing decisions per second.
We cut P99 metadata lookup latency by 91%, helping requests reach your pages faster and speeding up deployments along the way ↓
vercel.com/blog/how-we-cut-c…
What version are your bottom screenshots from? Thats not N64. They're way too dark. The original N64 game had better contrast. For example:
Steven ⬢ retweeted
You're gonna wanna read this one
Introducing Flat Rate CDN for Pro teams.
• Fixed monthly pricing in one predictable bill
• Premium global network performance
• Automatic protection for viral spikes
vercel.com/blog/introducing-…
"the one hole: every cost-conscious query goes to a competitor"
Good news, problem solved: xitter.cf/vercel/status/20973832…
Introducing Flat Rate CDN for Pro teams.
• Fixed monthly pricing in one predictable bill
• Premium global network performance
• Automatic protection for viral spikes
vercel.com/blog/introducing-…
You're gonna wanna read this one
Introducing Flat Rate CDN for Pro teams.
• Fixed monthly pricing in one predictable bill
• Premium global network performance
• Automatic protection for viral spikes
vercel.com/blog/introducing-…
Steven ⬢ retweeted
We closed 1,500 issues on 𝚟𝚎𝚛𝚌𝚎𝚕/𝚗𝚎𝚡𝚝.𝚓𝚜 in one month by building a 𝚌𝚕𝚘𝚜𝚊𝚋𝚒𝚕𝚒𝚝𝚢 agent with @eve.
The workflow:
1. Search related work
2. Try to reproduce bugs across versions in a sandbox
3. Return context for review
nextjs.org/blog/how-we-close…
