Theo SalvoI broke my splash site, and learned a few lessons about community, build vs buy, and sharpening the saw...
#humblefail #astrodotbuild
https://theodorejsalvo.com/humble-fail-is-tech-diy-worth-it/
Sarah Rainsberger@theo Loved your post, and appreciate that you appreciated the issue template. I'm sure @nmoo will be pleased!
"I’m running v2.9.7–which sounds like the latest version."
Oh, you sweet, summer child... 😅 It's true: update early, update often with Astro. Though, as the Docs Lead, I am campaigning on the slogan "Astro 5 ... in 2025!" It's exhausting for us, too!
nate@sarah11918 @theo Thanks for the tag Sarah! Very enjoyable read. ❤️
For some background, I copied most of the `astro-icon` issue template from the one on the main Astro repo! As it turns out, the whole team has slowly fine tuned that issue template over the years to be as actionable as humanly possible.
Users expect breaking changes to be absolutely exhausting, but I think Astro has found great ways to make them less of a mental burden. I've learned so much about good maintenance hygiene!
@theo By the way, we recently introduced a tool to automate this process for users! Running `npx @astrojs/upgrade` will walk you through any potentially outdated dependencies in your project and provide a link to the changelog.
Currently it's only for official `@astrojs/*` packages, but I'd love to add support for third-party integrations (like `astro-icon`) as well!
@nmoo I think that's where I went wrong. I accept full responsibility for breaking it--but I didn't check the astro version. If you can fix my bad behavior, then I'm all for it!