❓"When can we expect this feature"
Please refrain from asking this question towards open source maintainers. You generally shouldn't "expect" anything. I don't often agree with DHH but his take on OSS being a gift, not something you're entitled to, is something I relate with.
@danshappir.bsky.social do you find the approach we use to migrate to typescript / stricter checks something you can use?
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 🤘
I mean "not going with Node" is kind of exaggeration, no? There are already different kinds of registries and dependency managers, other than NPM
Woohoo! I can send slides and am available for any questions.
Best TLDR I have: template using pnpm to get super-isolated packages, allows each package in a repo to pick a different node.js version; allows 1 package to use scripts from another repo package (cross-node) and comes with builtin CI.
This is Leo. He is patiently waiting for this guy to throw the ball. Gonna be here a while. 13/10 (TT: twogoldenleos)
I know what my team next "video course" would be :))
Would love to come, that's the most interesting conf out there! However US is not the easiest destination for non-citizens :) and it seems there is no live remote option?
Wow, this message was full of typos and I blame my phone for this: are you up* and dependencies*
Btw @kixxauth.bsky.social are up for a talk about this project in devtools fm?
If you care about dependenciea and portable code composition I guarantee you, this would be very interesting! If not — I'm open to be publicly lynched!
I just saw pnpm supports JSR 👏. Now I'm only not sure since what version but I will check it out.
I need to listen to this! 🫶 We chose pnpm because with it, we can also use different runtimes for each project in the repo — e.g node14 for legacy project but also use node24 for e2e tests if they are isolated in another project).
I need to check if JSR supports that.
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
I wonder if chatting with AI will distort what is considered "ok way to communicate with peers" 😀
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?
Out of all possible human tasks, or even coding tasks, do you want to leave for us editing yaml files with obscure errors and slow feedback loop?
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
wow, it feels like you are going to look up a lot? I see 🔮️ neck problems in your future.
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 🥸
It's a very fitting logo of not-symmetric hexagons, I love it. It's obvious something needs to be aligned 😄️.
Anyways, thank you so much for eslint 🙇️. I've never stopped saying it's not just a code check tool — it's a learning tool for many people, and now it's a tool for AI context & correction.
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
I recently had someone in the team accidentally push to a repo without a protected main branch. I feel like this choice makes GitHub repo rules even more needed :)
