Youssef Gaber

Racing driver and CTO @SuhylHQ in my free time

[Jazz - the DB that syncs @jazz_tools]

the fun thing about being open-source is that you get drive-by PRs by typescript gods

https://t.co/7xxMJlSIXx

[Renault Clio Series @RenaultSeries]

🚨 A tighter 2026 calendar for more action, more intensity and more excitement.
Ready for another thrilling Clio Cup Series season? 🔥

[Renault Clio Series @RenaultSeries]

🎢 Snapshots from the Burgundy rollercoaster 📸

👉 https://t.co/0rqrovcj58
👉 https://t.co/l3gXgeVFrK

📸 DPPI / Alpine Racing

[Renault Clio Series @RenaultSeries]

𝗧𝗘𝗠𝗣𝗟𝗘 𝗢𝗙 𝗦𝗣𝗘𝗘𝗗! 𝗛𝗘𝗥𝗘. 𝗪𝗘. 𝗔𝗥𝗘. 👏🏼🇮🇹
It's time for the final races of the season this weekend in Italy. 🏆

#Renault #ClioCup

[Youssef Gaber @YGabrola]

@mattpocockuk Oh, are you trying to link back from global into a local package? Yeah, in this case `npm link [...]` wouldn't work, and you'd have to install the global -> local link using pnpm. I haven't tested but this should work `pnpm install pkg@link:$(npm prefix -g)/lib/node_modules/pkg`

[Youssef Gaber @YGabrola]

@mattpocockuk Under the hood, npm is just using the same exact mechanism as adding a `link:` dependency. Dependencies of linked dependencies are not resolved or installed, and this behavior is shared by all package managers. Even `pnpm link` docs mentions this specific use case but in reverse.

[Youssef Gaber @YGabrola]

@mattpocockuk It doesn't need to. `npm link` only creates the symlinks from it's global node_modules & bin into your local package directory. It doesn't resolve or install deps, because the local node_modules it's symlinked into should have all deps already installed (by pnpm in this case).

[Youssef Gaber @YGabrola]

@izs And actually it seems like a simple problem to solve, but it's actually kinda hard to understand fully and hard to explain. It's one of these problems where you expect some tool to just do everything for you without having to get so much into the weeds to fix it yourself

[Youssef Gaber @YGabrola]

@izs The amount of pain I've been through to fix our tooling to get our library to work whenever we get bug reports was insane. So when something has been quite a pain in the tushy for so long, and something comes to solve it like some magic pill, you can't help but love it this much

[Youssef Gaber @YGabrola]

@mattpocockuk I've found that the best tool to do this is `tshy` by @izs. It is quite opinionated but if there's someone's opinions are to follow, it would be npm's creator! The amount of tooling code that I've deleted since moving to `tshy` is insane!

[Youssef Gaber @YGabrola]

@mattpocockuk I can go into so much detail into why this is better, but the tl;dr is that it works even if `exports` is not supported or if .cjs/.mjs extensions are not supported/causing problems.

[Youssef Gaber @YGabrola]

@webdevcody FYI, Wasm is extremely slower than usual when dev tools is open

[Youssef Gaber @YGabrola]

@dhh I know you said it's not the same thing, but there's also something elegiacally poetic about how IOPS, throughput, and disaster recovery capabilities will die a beautiful death if you move from the cloud to a single hard drive.