mirror of
https://codeberg.org/forgejo/forgejo.git
synced 2024-11-15 07:09:47 +01:00
119 lines
2.9 KiB
Markdown
119 lines
2.9 KiB
Markdown
|
---
|
||
|
date: "2021-07-20T00:00:00+00:00"
|
||
|
title: "npm Packages Repository"
|
||
|
slug: "packages/npm"
|
||
|
draft: false
|
||
|
toc: false
|
||
|
menu:
|
||
|
sidebar:
|
||
|
parent: "packages"
|
||
|
name: "npm"
|
||
|
weight: 60
|
||
|
identifier: "npm"
|
||
|
---
|
||
|
|
||
|
# npm Packages Repository
|
||
|
|
||
|
Publish [npm](https://www.npmjs.com/) packages for your user or organization.
|
||
|
|
||
|
**Table of Contents**
|
||
|
|
||
|
{{< toc >}}
|
||
|
|
||
|
## Requirements
|
||
|
|
||
|
To work with the npm package registry, you need [Node.js](https://nodejs.org/en/download/) coupled with a package manager such as [Yarn](https://classic.yarnpkg.com/en/docs/install) or [npm](https://docs.npmjs.com/downloading-and-installing-node-js-and-npm/) itself.
|
||
|
|
||
|
The registry supports [scoped](https://docs.npmjs.com/misc/scope/) 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.
|
||
|
|
||
|
```shell
|
||
|
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]({{< relref "doc/developers/api-usage.en-us.md#authentication" >}}). |
|
||
|
|
||
|
For example:
|
||
|
|
||
|
```shell
|
||
|
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:
|
||
|
|
||
|
```shell
|
||
|
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:
|
||
|
|
||
|
```shell
|
||
|
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.
|
||
|
|
||
|
## Install a package
|
||
|
|
||
|
To install a package from the package registry, execute the following command:
|
||
|
|
||
|
```shell
|
||
|
npm install {package_name}
|
||
|
```
|
||
|
|
||
|
| Parameter | Description |
|
||
|
| -------------- | ----------- |
|
||
|
| `package_name` | The package name. |
|
||
|
|
||
|
For example:
|
||
|
|
||
|
```shell
|
||
|
npm install @test/test_package
|
||
|
```
|
||
|
|
||
|
## Tag a package
|
||
|
|
||
|
The registry supports [version tags](https://docs.npmjs.com/adding-dist-tags-to-packages/) which can be managed by `npm dist-tag`:
|
||
|
|
||
|
```shell
|
||
|
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:
|
||
|
|
||
|
```shell
|
||
|
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.
|
||
|
|
||
|
## Supported commands
|
||
|
|
||
|
```
|
||
|
npm install
|
||
|
npm ci
|
||
|
npm publish
|
||
|
npm dist-tag
|
||
|
npm view
|
||
|
```
|