Incidentally I once ran into a mature package that had lived in the 0.0.x lane forever and treated every release as a patch, racking up a huge version number, and I had to remind the maintainer that users depending with caret ranges won't get those updates automatically. (In semver caret ranges never change the leftmost non-zero digit; in 0.0.x that digit is the patch version, so ^0.0.123 is just a hard pin to 0.0.123). There may occasionally be valid reasons to stay on 0.0.x though (e.g. @types/web).

▲

robin_reala a day ago | parent | next [-]

Presumably they’re following https://0ver.org/

▲

BobbyTables2 11 hours ago | parent | prev | next [-]

Isn’t vim or bash kinda like that? One of them publishes something like a few hundred patches on top the released tarball…

▲

jve a day ago | parent | prev [-]

Maybe that is intentional? Which package is it?

▲

aragonite a day ago | parent | next [-]

It's the type definitions for developing chrome extensions. They'd been incrementing in the 0.0.x lane for almost a decade and bumped it to 0.1.0 after I raised the issue, so I doubt it was intentional:

https://www.npmjs.com/package/@types/chrome?activeTab=versio...

	▲	creatonez a day ago \| parent [-]
		This is part of the DefinitelyTyped project. DT tends to get a lot of one-off contributions just for fixing the one error a dev is experiencing. So maybe they all just copied the version incrementing that previous commits had done, and no one in particular ever took the responsibility to say "this is ready now".

▲

CITIZENDOT a day ago | parent | prev [-]

threejs ?