i usually just add all shadcn components at once to avoid the back and forth. easy setup, but then i end up with 40+ component files and use maybe 4 of them.
kept finding leftover files i had no idea were even there. couldn't tell which ones were safe to delete without tracing imports manually.
so i vibe coded a tiny package for it.
- npm install -g dead-files
run dead-files in any project. scans everything, builds a reverse import map, prints every file nothing imports.
also has an interactive mode. run dead-files -i and you get a checkbox list of all unused files. pick what you want to delete, confirm once, done.
handles ts path aliases, next.js pages, config files. knows not to flag those as unused.
~8kb download.
npm: https://t.co/5kJC8k92cd
repo: https://t.co/hZY2dNj1Us
First time a company is cutting jobs because of AI at @block. We knew it would happen someday but seeing it for real hits different. The worst part is the market is happy and the stock jumped 24%.
we're making @blocks smaller today. here's my note to the company.
####
today we're making one of the hardest decisions in the history of our company: we're reducing our organization by nearly half, from over 10,000 people to just under 6,000. that means over 4,000 of you are being asked to leave or entering into consultation. i'll be straight about what's happening, why, and what it means for everyone.
first off, if you're one of the people affected, you'll receive your salary for 20 weeks + 1 week per year of tenure, equity vested through the end of may, 6 months of health care, your corporate devices, and $5,000 to put toward whatever you need to help you in this transition (if you’re outside the U.S. you’ll receive similar support but exact details are going to vary based on local requirements). i want you to know that before anything else. everyone will be notified today, whether you're being asked to leave, entering consultation, or asked to stay.
we're not making this decision because we're in trouble. our business is strong. gross profit continues to grow, we continue to serve more and more customers, and profitability is improving. but something has changed. we're already seeing that the intelligence tools we’re creating and using, paired with smaller and flatter teams, are enabling a new way of working which fundamentally changes what it means to build and run a company. and that's accelerating rapidly.
i had two options: cut gradually over months or years as this shift plays out, or be honest about where we are and act on it now. i chose the latter. repeated rounds of cuts are destructive to morale, to focus, and to the trust that customers and shareholders place in our ability to lead. i'd rather take a hard, clear action now and build from a position we believe in than manage a slow reduction of people toward the same outcome. a smaller company also gives us the space to grow our business the right way, on our own terms, instead of constantly reacting to market pressures.
a decision at this scale carries risk. but so does standing still. we've done a full review to determine the roles and people we require to reliably grow the business from here, and we've pressure-tested those decisions from multiple angles. i accept that we may have gotten some of them wrong, and we've built in flexibility to account for that, and do the right thing for our customers.
we're not going to just disappear people from slack and email and pretend they were never here. communication channels will stay open through thursday evening (pacific) so everyone can say goodbye properly, and share whatever you wish. i'll also be hosting a live video session to thank everyone at 3:35pm pacific. i know doing it this way might feel awkward. i'd rather it feel awkward and human than efficient and cold.
to those of you leaving…i’m grateful for you, and i’m sorry to put you through this. you built what this company is today. that's a fact that i'll honor forever. this decision is not a reflection of what you contributed. you will be a great contributor to any organization going forward.
to those staying…i made this decision, and i'll own it. what i'm asking of you is to build with me. we're going to build this company with intelligence at the core of everything we do. how we work, how we create, how we serve our customers. our customers will feel this shift too, and we're going to help them navigate it: towards a future where they can build their own features directly, composed of our capabilities and served through our interfaces. that's what i'm focused on now. expect a note from me tomorrow.
jack
I kept hitting limits in Claude while coding and had to wait hours to continue.
Then I started using different models for different tasks. Now it runs so much better.
Here’s exactly what I do:
1. Opus 4.6 (Plan mode)
- Only when I start a new project or new feature
2. Sonnet 4.6
- To turn the plan into actual code
3. Haiku
- For any questions about the code or just talking about the project
This saves me a lot of time.
Would love to know if there's a way to switch models automatically.
@shadcn This is gonna be insanely useful 🔥
Thanks @shadcn for existing (and for dropping these CLI upgrades that actually matter).
I genuinely can’t remember the last time I used anything else for my projects’ UIs 😅
Style Applier is officially live on the @webflow App Marketplace!! 🚀
I came up with the idea for Style Applier when we were building @MiyagiAgents .
One of the use cases I loved was being able to paste CSS that I grabbed from Figma dev mode, and having Miyagi apply that CSS to elements in Webflow.
This really saved times for elements that had gradients, box shadows, and blurs.
BUT, it wasn't perfect...
Miyagi took 30-60 seconds to handle that process AND since it was done by AI there was allways going to be a cost involved, so it couldn't be free.
So we set out to build a dedicated app for this specific use case to make it even better.
Here's some things we improved:
✅ Processing time cut from 30+ seconds to <3 seconds.
✅ Built in Auto Conversion from PX to REM
✅ UI to change which state you want to apply the CSS to
And best of all, it isn't using AI, so Style Applier will be completely FREE, forever.
Hope ya'll enjoy! ❤️
The Amply Holiday Challenge is Live!!! 🎄
We teamed up with @Webflow to create a fun challenge to end the year with up $4000 prizes up for grabs 🎊
We wanted a challenge that:
✅ People could participate in with a few hours of time
✅ Open to all skill levels
✅ Gets the community engaged
✅ Encourages Creativity
✅ Most importantly, is FUN!
We had a ton of fun building this out! We built a full app to gamify the process and help us manage the challenge. Through the dashboard you can:
🎁 Complete challenges (Reviewed by AI)
🎅 Earn points that boost your chances in the raffle
🖥️ See other submissions
🏁 See where you stack up on the leaderboard
(ps Webflow code components were an AWESOME way to bring components from the app into our landing page easily)
Huge shoutout to our judges who will be helping us to decide on the winners:
@arrr_morgan, @HalZeitlin, @verofashoo, @sebasbimbi, @ale_sannazzaro
Please help us get the word out to the whole community by liking & sharing this post!