npm Package Registry
Publish npm packages for your user or organization.
Requirements
To work with the npm package registry, you need Node.js coupled with a package manager such as Yarn or npm itself.
The registry supports scoped and unscoped packages.
The following examples use the npm
tool with the scope @test
.
Configuring the package registry
To register the package registry you need to configure a new package source.
NOTE: in the example below (npm config set -- '//forgejo...
) the leading scheme, https:
, is intentionally missing. It must not be included. The following is incorrect: npm config set -- 'https://forgejo...
Parameter | Description |
---|---|
scope | The scope of the packages. |
owner | The owner of the package. |
token | Your personal access token. |
For example:
or without scope:
Publish a package
Publish a package by running the following command in your project:
You cannot publish a package if a package of the same name and version already exists. You must delete the existing package first.
Unpublish a package
Delete a package by running the following command:
Parameter | Description |
---|---|
package_name | The package name. |
package_version | The package version. |
For example:
Install a package
To install a package from the package registry, execute the following command:
Parameter | Description |
---|---|
package_name | The package name. |
For example:
Tag a package
The registry supports version tags which can be managed by npm dist-tag
:
Parameter | Description |
---|---|
package_name | The package name. |
version | The version of the package. |
tag | The tag name. |
For example:
The tag name must not be a valid version. All tag names which are parsable as a version are rejected.
Search packages
The registry supports searching but does not support special search qualifiers like author:forgejo
.