Post

Wrote a RFC for @npmx.dev The idea: surface packages that are silently bundled inside other packages' tarballs — and show their "implied downloads". Would love feedback 👇 github.com/npmx-dev/npm... Also applied to @e18e.dev

github.com[RFC] Surface Inline Bundled Dependencies in Package Pages · Issue #1736 · npmx-dev/npmx.devSummary Add first-class UI support for packages that physically inline their dependencies into their published tarball — making it possible for developers and consumers to understand what packages ...

28/2/26, 6:01 am8 reposts61 likes

Kevin Deng

@sxzz.dev

28 Feb

Followed up with a separate RFC at e18e to discuss the `inlinedDependencies` field as a broader ecosystem standard — naming, shape, and adoption — since it's relevant beyond npmx itself. If you're interested in the standard side of things, come join the discussion there: github.com/e18e/ecosyst...

github.comIntroduce `inlinedDependencies` Field in `package.json` · Issue #237 · e18e/ecosystem-issuesSummary Propose a new inlinedDependencies field in package.json as a community convention for explicitly declaring which dependencies are physically inlined into a published tarball — regardless of...

naugtur

@naugtur.pl

28 Feb

We don't know if they're the same thing or not. Bundled deps are messy. And should be a reason to show a warning. Overview of what there is: github.com/naugtur/rese... I also noticed some packages contain much more bundled deps than they list in pkg.json and Node would just load them

This is a great idea! I'm slightly sceptical of being able to estimate the downloads numbers from this. I'll try to formulate my thoughts when I'm at a computer.