Package Registry for NPM doesn't support search API endpoints #9116

New Issue

GiteaMirror · 2025-11-02T08:29:54-06:00

GiteaMirror commented

2025-11-02 08:29:54 -06:00

Originally created by @jackv24 on GitHub (Jun 23, 2022).

Feature Description

The new NPM package registry is a great addition!

I'm trying to use it to host packages for the Unity Package Manager, to replace Verdaccio and have everything in one place. It seems like the Gitea registry has the same limitation as GitHub packages mentioned here. Their specific note is:

...doesn't support any of the NPM search API endpoints (/-/all or /-/v1/search)

This is the only blocker to moving over, it would be awesome if this was supported.

Screenshots

No response

Originally created by @jackv24 on GitHub (Jun 23, 2022). ### Feature Description The new NPM package registry is a great addition! I'm trying to use it to host packages for the Unity Package Manager, to replace Verdaccio and have everything in one place. It seems like the Gitea registry has the same limitation as GitHub packages [mentioned here](https://forum.unity.com/threads/using-github-packages-registry-with-unity-package-manager.861076/). Their specific note is: > ...doesn't support any of the NPM search API endpoints (/-/all or /-/v1/search) This is the only blocker to moving over, it would be awesome if this was supported. ### Screenshots _No response_

GiteaMirror added the topic/packages type/feature type/proposal labels 2025-11-02 08:29:54 -06:00

GiteaMirror closed this issue

2025-11-02 08:29:54 -06:00

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/gitea#9116