bd4c7ce578
This PR cleans up the docs in a way to make them simpler to ingest by our [docs repo](https://gitea.com/gitea/gitea-docusaurus). 1. It includes all of the sed invocations our ingestion did, removing the need to do it at build time. 2. It replaces the shortcode variable replacement method with `@variable@` style, simply for easier sed invocations when required. 3. It removes unused files and moves the docs up a level as cleanup. --------- Signed-off-by: jolheiser <john.olheiser@gmail.com>
3.5 KiB
| date | title | slug | sidebar_position | draft | toc | menu | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2021-07-20T00:00:00+00:00 | npm Package Registry | npm | 70 | false | false |
|
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.
npm config set {scope}:registry https://gitea.example.com/api/packages/{owner}/npm/
npm config set -- '//gitea.example.com/api/packages/{owner}/npm/:_authToken' "{token}"
| Parameter | Description |
|---|---|
scope |
The scope of the packages. |
owner |
The owner of the package. |
token |
Your personal access token. |
For example:
npm config set @test:registry https://gitea.example.com/api/packages/testuser/npm/
npm config set -- '//gitea.example.com/api/packages/testuser/npm/:_authToken' "personal_access_token"
or without scope:
npm config set registry https://gitea.example.com/api/packages/testuser/npm/
npm config set -- '//gitea.example.com/api/packages/testuser/npm/:_authToken' "personal_access_token"
Publish a package
Publish a package by running the following command in your project:
npm publish
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:
npm unpublish {package_name}[@{package_version}]
| Parameter | Description |
|---|---|
package_name |
The package name. |
package_version |
The package version. |
For example:
npm unpublish @test/test_package
npm unpublish @test/test_package@1.0.0
Install a package
To install a package from the package registry, execute the following command:
npm install {package_name}
| Parameter | Description |
|---|---|
package_name |
The package name. |
For example:
npm install @test/test_package
Tag a package
The registry supports version tags which can be managed by npm dist-tag:
npm dist-tag add {package_name}@{version} {tag}
| Parameter | Description |
|---|---|
package_name |
The package name. |
version |
The version of the package. |
tag |
The tag name. |
For example:
npm dist-tag add test_package@1.0.2 release
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:gitea.
Supported commands
npm install
npm ci
npm publish
npm unpublish
npm dist-tag
npm view
npm search