Post

Some critical projects like @typescriptlang.org don't (or can't) follow SemVer. They suggest users pin versions in package.json. But what if npm package versions could explicitly *declare* their compatibility range. Clients could further constrain ranges for upon opt in. Best of both worlds.