npmx maintainer here! a few answers to questions i see:

we haven’t launched yet! we’re building openly but aiming for march 3. as is par for the course, hn gets the scoop.

i made the first commit two weeks ago, so it’s very new. but we’ve had 900+ PRs and 170+ contributors in the last fortnight… because this is something we care about.

having said that, i’m taking notes about what is and isn’t intuitive

npmjs remains the source of truth for the registry, which is why we get our data from there

but along the way we add a lot of features, like: - claiming new packages from the ui - batch admin operations for your orgs, teams and packages - total install size, vulnerabilities and deprecations for your transitive dependencies - generated docs for packages - linkable package contents - and more

▲

tcper 5 hours ago | parent [-]

Do you have your own dependency resolution algorithm? Can we have the most lightweight node_modules directory?

	▲	danielroe 5 hours ago \| parent [-]
		we do have an algorithm to calculate total install size it’s not _exactly_ the same as if you install with npm and check the size of your node_modules but it’s a pretty good proxy having said that, there’s room to make it better