Changes stream to implement followers webhooks are a functional alternative.Īdditionally, any search terms used are not passed to upstream repositories and are handled by Cloudsmith.Creating tokens via npm token use the cloudsmith-cli or UI instead.Viewing and changing collaborators of packages via 'npm owner'.npm access and visibility packages follow repository visibility.Profile, user, team or org commands use the cloudsmith-cli instead.Unless otherwise specified we'll be working on removing these limitations in a near-future release.Ĭloudsmith is unlikely to support the following (out-of-scope): If uploading using the cloudsmith-cli, then the absolute maximum size per-package file limit will be the standard 5GiB. The maximum size per-package file is currently limited to 100MiB (100 megabytes), but only when utilising the native npm-cli for publishing.The Cloudsmith npm registry implementation currently has the following limitations: You can find out more about distribution tags in the npm documentation (external link). You can also remove tags from a package: npm dist-tags rm PACKAGE_NAME TAG -registry= You can add tags to a package: npm dist-tags add _VERSION TAG. You can inspect a package to see what tags it has: npm dist-tags ls PACKAGE_NAME -registry= If the latest package is moved/deleted, then existing packages are sorted via SemVer to determine the next latest.

When a package is copied/moved to another repository, its tags are carried with it.When a package that is latest is deleted, the tag is moved to the next applicable version by semver.Unless specified otherwise, the default tag for the last package published is latest.A package version may have multiple unique tags.A specific tag can point at one version of a package only.Distribution tags allow npm packages to be tagged with a mnemonic that is associated with a specific package version.Ĭloudsmith has full support for distribution tags and (mostly) follows the same rules for them as on :

Npm config set registry to default