hades is a fun game

i will be at viteconf in a couple of weeks. come say hi if you see me! 🎉

What tools or libraries do you wish were faster?

New release of clack alpha 🥳 Bunch of bug fixes in this one. If you're building a cli, give it a whirl!

a thing i put together at the weekend coming soon? 😀

eslint-plugin-depend released! this ESLint plugin helps you find dependencies the @e18e.dev community has recommended replacing thanks to @bluwy.me for adding eslint/json support too 🙏

gm bluesky how is it that @e18e.dev still only has 2.3K followers come on, y'all nerds value performance a whole lot more than that

Started the day landing 5 PRs with @crutchcorn.dev 🍻

remember if you're using vitest to test a terminal app, set FORCE_COLOR=1 in your vitest config's `env` otherwise snapshots will _not_ have colour (vitest turns them off by default) assert against what a human will see!

what i've found LLMs useful for recently: figuring out unocss, tailwind and whatever else class names no way i can be bothered remembering those 😂

can someone aware of node internals answer me this: will node _always_ fire an 'exit' event? there's so much poorly written code out there that tries to brute force doing something on exit (listens to all possible exit events and signals). but i feel like this must not be necessary?

the svelte-check profiling lead to this getting merged which reduces a svelte-check run in shadcn-svelte from 12s to 8s! super happy to have taken part in this :D

if i have a 50M/week downloads package then split it up into 100 packages the root one depends on - does tidelift pay me ${100*N}?

its good fun seeing package managers do the most difficult part of software engineering: naming things npm: `before` yarn: `npmMinimalAgeGate` pnpm: `minimumReleaseAge`

another day, another library move to trusted publishing & provenance: tinyspy 🎉 thanks to @erus.dev setting this up

Would love to see more packages deprecated on npm So many have deprecation notices in their readme but haven't actually been deprecated. I wonder what the reason for that is 🤔

some evening hackery making svelte-check run 6 seconds faster! 🤌

again running into the node test runner funkiness src - sources, lib - tsc output, {src,lib}/test - tests 20.x - works 24.x - node tries to run `*.ts` all good lets turn off type stripping: 20.x - no such option 24.x - works damn! lets try a glob: 20.x - no such file (no globs!) 24.x - works

in light of the current supply chain attacks, I've just published a @github.com action to detect packages that _lose_ their provenance. 📦 supports pnpm-lock.yaml, package-lock.json, yarn.lock (v1) 🎨 inline GitHub annotations ✅ JSON output + configurable 💪 published in TS with zero deps

just an observation: - clack, 350KB, entire CLI rendering framework - boxen, 700KB, draws boxes

often we look at frameworks and libs in isolation when dealing with perf. we should be looking at the real world uses more often this is just a quick repo of package.json files made from various starter kits and linked up to npmgraph

reminder that node-modules.dev shows whether a package is trusted or published w/ provenance node-modules.dev

we're working on another idea in e18e thats built using svelte and should help visualise/communicate some of these clean up efforts got any svelte folk who fancy chipping in? 😀

A view I often struggle with is: > unless a speed up is noticeable by users, it isn't worth the effort Sometimes we know a function performs 1M ops/sec vs current 300k ops/sec But they only call it once so it isn't worth the change

Established packages like eslint are some of the last ones propping up bloated dependencies If we had an easier way to measure perf and size, maybe we could get some movement there 👀

maybe i should join more podcasts and streams 👀

gone down a YAML parsing rabbit hole

That’s it, Multiocular is now at MVP stage. I’ll be using it in my own projects to see if the “core loop” works. If people find it useful, I’ll add CI and smart checking later, so it can automatically flag suspicious patterns. github.com/multiocular-...

finally getting around to sorting this wrapping feature in clack 👀

did a rework of something on a branch, not realising i did a separate rework on another machine and forgot to pull it down conflict hell! 😅

looking forward to the day dual packages cease being a thing

Re the incidents lately: I think npm needs to provide a flow where we can block a workflow (gh action) until a user goes to a URL to 2fa and approve it Most of us maintainers would be happy to do that extra step imo

This is the way. Super happy to have contributed to this project and see it leading by example

some thoughts about the bloat introduced by edge-case first libraries

trying to put a blog post together 👀

also fun metrics from today's compromise 73 million downloads a week of 9 lines of code to check if something is an array ah and its 54KB because a yarn error log was accidentally published in the package 7 years ago

even though the compromised packages are gone now, im so happy to see the @e18e.dev community acting fast - coming up with a plan to help upgrade and remove packages that were affected by this there's already a tracking issue and bunch of PRs to upgrade deps, remove old ones, etc

everyone loves a bit of chaos every now and then

another one... all of them are plain old phishing. lets just stop reading emails

tinyglobby is such a good success story. It has replaced many libraries with something faster, smaller and more modern @superchupu.dev has done excellent work here, and @benmccann.com has driven adoption so well Cherry on top is that much of this happened inside @e18e.dev 🩵

it only has one rule right now but here's the YAML ESLint language i implemented

there's already a yaml eslint plugin but i wanted to have a go at implementing a yaml eslint language (like eslint/json, eslint/css, etc) it works!

making an ESLint language plugin 👀

copilot inside a github repo has been super useful for understanding not-so-well-documented projects, especially internals etc

Another social tonight 🙌 catching up with people is my second job 😅

an increasingly common thing i've noticed in oss - nobody has a windows machine to test against 😅

reviewing a bunch of good PRs this evening - storybook migrating to empathic - svelte CLI QoL stuff around internal type definitions - e18e CLI docs

big thanks to @outslept.bsky.social and others of the @e18e.dev community on adding more migration docs! these are already proving to be super useful

we have a conversation in the e18e discord at the min around why generators are so much slower than a regular iterator anyone who knows v8 and/or node internals better than us want to educate us? 😄

i do miss having a budget for conferences 😅 if anyone wants to sponsor me getting to squiggle, perf now or vue fes japan - ill be your best friend 😂