It's not just Luke's opinion.
By volume Temporal has more tests and more lines of spec text than any previous JavaScript feature βοΈ
It's not just Luke's opinion.
By volume Temporal has more tests and more lines of spec text than any previous JavaScript feature βοΈ
a screenshot of a chart showing the install size difference of versions of the "yaml" package. the 3.0.0 package has 268KB while the previous versions have 660KB+
look at that lovely yaml@3.0.0 bar π
what a great change by Eemeli here, going ESM-only and more than halving the size
packages shouldn't polyfill features they need.
users should polyfill features the package needs.
we do this in browsers, so why not in node?
from some of @willow.sh's npm data project:
largest tarball: 196MB
average tarball: 430KB
smallest tarball: 132B
this isn't even the whole registry yet π
TypeScript 6.0 Beta is out π
πΆ Temporal
πΆ Map#getOrInsert
πΆ RegExp.escape
πΆ #/ prefix for Package Imports
New defaults!
πΆ --target=ES2025
πΆ "use strict"
π· --strict
Deprecations!
ποΈ baseUrl, outFile
ποΈ import assertions
ποΈ `module` namespaces
ποΈ module: amd
ποΈ moduleResolution: node
ποΈ target: ES5
today:
released a major of nuxt/test-utils (v4) β
released a minor of nuxt/telemetry (removed 10/15 deps!) π₯
released two new patches of nuxt β
and now a glass of π·
today we distributed some of our sponsors fund to a few people for their great work:
- @hyeseong.kim
- @webpro.nl
- @devminer.xyz
- @superchupu.dev
- @lukeed.bsky.social
thanks so much to you all for being part of the community and helping out so many of us. your work is incredibly valuable π
The new website's page for the 'is-even' package, with a warning flagging it as unnecessary.
The better npm site got warnings on packages that should be avoided yesterday.
Big thanks to the @e18e.dev community for making that easy!
The best npm directory has the sparkline. It also unfolds a larger chart, to explore download stats in depth.
Come join us to the hottest open source project !
You know where we are :)
β did you know about nuxt.care? it's an amazing project created by @flo-heuberger.bsky.social to help the nuxt modules ecosystem
there's an PR to add it to devtools, and I've already added the badge to lots of my modules
I'm asking because I'm building an alternative to npmjs.com, including the admin ui piece
I have a working mvp, although of course it's very π§
if this is something you'd like to contribute to, and you've experienced any of these pain points, let me know - always more fun to build together! π
π₯ amazing PR just merged from @wlls.dev using @deno.land's docs package to generate docs for any package on the npm registry ....
π¦ Calling all Rustaceans!
Weβre migrating Rolldown `fake-js` plugin to Rust to supercharge build speeds! π
We currently use Babel but want to move to Oxc for better performance.
Check the issue β¬οΈ
github.com/sxzz/rolldow...
Oxlint rules page can be sorted now.
oxc.rs/docs/guide/...
one of the stacks nobody has managed to modernise yet IMO: jest.
297 packages, 28MB.
interestingly much of the dep tree is owned by only a couple of individuals, too.
new release of the @e18e.dev github action for diffing dependency changes
it'll now more cleanly show changes in dependency size
Every time you update your dependencies and see that your deps tree gets slimmer, there is a high chance you're enjoying the relentless work of James or other folks from the @e18e.dev community that he inspired to get into action. Consider sponsoring him if you care about the JavaScript ecosystem.
just a reminder that i have github sponsors if you'd like to sponsor the OSS work i do.
i maintain quite a few projects, and contribute to many more. nobody other than these sponsors pay for that. so these help a huge amount, however small π
thanks so much to those who already did β€οΈ
I'm delighted to announce the first alpha of `@nuxt/a11y` π
βͺ new core nuxt module
βͺ integrated in nuxt devtools
thanks to @timdamen.io for his incredible work on this β€οΈ
you can test it today β we'd love feedback, ideas, issues + PRs π
This list is nothing short of amazing projects. Last year, Knip would've probably ended up even higher than this year. What other tooling is missing here?
tsdx by Jared Palmer upgraded to modern tooling, including bunchee, vitest, oxlint, oxfmt and bun.
PR: github.com/jaredpalmer/...
βοΈ Knip Extension v1.0.0 is out
For VS Code + Open VSX (e.g. Cursor)
βΆοΈ Install the Knip extension, tell your coding agent to "configure knip" or "fix up knip config" and... profit!
Comes with MCP Server + custom guides + incremental docs for a generated A+ Knip config β¨
Clean code β redefined.
Oxc -> vuejs/core π
PR:
* github.com/vuejs/core/p...
* github.com/vuejs/core/p...
screenshot of passing binary data down as props
new RSC Explorer example: binary data
rscexplorer.dev?s=binary
fast-equals went from 280KB to 100KB in the last release! π
we still use dequal in most places but this is handy for where you need to compare more complex values
thought i'd dig through the esm vs cjs dataset to see if there's any i can contribute a migration to
many of the top few hundred, though, are packages we shouldn't even need anymore π
Announcing Oxlint Type-Aware Linting Alpha π
β‘ Fast via tsgo (TypeScript 7)
π Type-checking while linting
βοΈ Rule configuration
π Highly demanded no-deprecated rule
oxc.rs/blog/2025-1...
Do you think it's confusing how linters and TypeScript both get the same red squiggly color by default in VS Code? But you don't want to downgrade lint reports all the way to orange?
Please upvote my VS Code feature request to add a "danger" style between orange and red! github.com/microsoft/vs...
βοΈ Knip v5.72.0 is out
β New SASS/SCSS compiler
β New SVGR plugin
β Support tsconfig `references` + `rootDirs` (oxc-resolver)
β Improved & prettier export `--trace`
β Extended AGENTSβ.md to assist w/ coding & new plugins
..and a whooole lot more
Knip: knip.dev
Changelog: github.com/webpro-nl/kn...
Merged! Vitest 4.0.14 includes a new tabbed view and slider for visual regression reports π
This feature required a lot of work under the hood, including the creation of the new test artifacts API. Really curious to see how it'll be used by us and the ecosystem π