A few days later: 🎥 Here's the video of me and Steve Edwards exploring how to avoid projects getting stuck with old tech! youtu.be/NinguUAIq7c?...

🎙️ I was a guest at my favourite podcast JavaScript Jabber!

Had the pleasure to dive in ✅️ breakproof.dev with Steve and geek out about resilient yet easy-to-upgrade software.

Give it a listen: open.spotify.com/episode/5PXTuXCnlUDowuV0FGT0vq

Thank you @danshappir.bsky.social for making this happen!

If anybody at Microsoft ever gets budget/headcount for a full-time employee at npm, please reach out to me. I would love to clean up this very important, somewhat underserved website. 🥲

I just became a sponsor of @manuelschiller.bsky.social ! Would recommend it! Manuel is one of the sharpest minds I know, doing wonders with Tanstack Start & the tantack packages as a whole 🤘

This is Leo. He is patiently waiting for this guy to throw the ball. Gonna be here a while. 13/10 (TT: twogoldenleos)

Better late than never 👀:

lnkd.in/djGuvjTc

In 2 days I'm talking (in Bulgarian) about building software that lasts; in particular the open source project breakproof.dev that Yotpom.com uses internally

0 deep abstractions — using tools directly in a way to help NOT only developers but AI & CI too

With the changes to the lockfile format and the new types of fetchers that were added to pnpm, now it is really easy to make pnpm an installer for anything

bsky.app/profile/pnpm...

Which 𝘀𝘁𝘆𝗹𝗲 makes it clear the function returns an array?

Why TS team uses `𝗧𝘆𝗽𝗲[]` for error msgs? Isn't the utility `𝗥𝗲𝗰𝗼𝗿𝗱<𝗧𝘆𝗽𝗲>` showing the preference? Isn't `𝗧𝘆𝗽𝗲[][]` sillier when compared to `𝗔𝗿𝗿𝗮𝘆<𝗔𝗿𝗿𝗮𝘆<𝗧𝘆𝗽𝗲>>`, especially if you read it out load.

I feel there is a clear winner?

Training copilot specifically to agentically iterate over @github.com actions (being able to run them & read the errors) would save humans DECADES 😌️ Even with all of `actionlint, `act` and/or git pushes, the github CICD dev process is stuck in the past, prone to TON of sneaky AI hallucinations

Our team did a 3 day intense onsite planning our next big project, and here the top 3 rules for us & AI:

1) surface errors as-early-as-possible (think ~TS & ~lint)
2) mock as-close-as-possible-to-production (think ~MSW)
3) clearly separate vendor-specific logic (our needs vs framework or lib)

I ❤️ the pod about errors on @syntax.fm! 1 extra thing maybe worth mentioning @wesbos.com @tolin.ski is that errors often get falsely "silenced" because "catch" catches all errors and devs don't check the type. That's why in yotpo.com we lint all catch statements to make sure error type is verified 🤌

Moving codebases to newer or stricter TS in 1 go is often impossible (can't stop dev for so long, risk many bugs at once or know all the correct types)

In breakproof.dev we snapshot existing errors and fail only for new ones. Allows us to upgrade TS or make it stricter now, and gradually fix errors

What a timing! Latest #jsjabber not only mentions but dedicates episode to JS->TS migration.

@danshappir.bsky.social I got so much I want to say🥴, but maybe start with: there is a way to just rename all files to `.ts` (without any code changes) AND have strict mode at the same time 🥸

Ton of npm libs use github.com/cosmiconfig/... to load their config files. But, today I learned, if nodejs dies, the temporarily file created by cosmiconfig remains 🤷‍♂️

I fixed this locally in 5 mins thanks to the amazing patch ability of @pnpm.io (kudos @kochan.io!) and the LLMs era of code editors

Quite nice little educational tool — seeing the difference between bundlers outputs.

𝘀𝗸𝗶𝗽𝗟𝗶𝗯𝗖𝗵𝗲𝗰𝗸 is a 𝗧𝗦 config for skipping 𝗧𝗦 checks of libraries, 𝘳𝘪𝘨𝘩𝘵? 𝗡𝗼

It only skips checks for .𝗱.𝘁𝘀 files. If you develop a 𝗧𝗦 lib in your own monorepo used only by your projects, you still must run 𝘁𝘀𝗰 for your lib. Otherwise checking your project for TS errors will also show the lib errors

In the latest #jsjabber episode, @danshappir.bsky.social mentioned (once again) the dreaded topic: "how to move to typescript from js". If by chance you see this, in yotpo.com we are using one maybe interesting approach with breakproof.dev where we snapshot existing TS errors and stop new ones