Some packages from Custom Registry are not displayed

Unity Engine
,
1

Hello! I recently set up my private npm registry on Verdaccio, but I noticed that not all of my packages are displaying in Unity. Instead of 40+, I only see 20 :(. Even searching for the invisible packages doesn’t yield any results.
The scoped registry is configured correctly.

scope: com.<org-name>```
All packages have the specified prefix in their names.

This is happening on both Unity 2022.3 and 2023.2 in different projects. "package.json" files do not differ significantly.
However, I can see them in npm (using npm show com.<org>.<package-name>).
2

Hi @g0dzZz1lla ,

I’m sorry you’re running into these issues. First, have you checked the Editor.log or upm.log files for hints about what could be wrong?

If you see nothing there, it might be a problem with what Verdaccio returns. Npm registries implement either npm’s legacy “/-/all” endpoint or the more recent “/-/v1/search” endpoint. These are what feeds the Unity Package Manager when listing available packages by registry.

To my knowledge, Verdaccio implements the legacy “/-/all” endpoint only. Do you see all the packages when you navigate to the “/-/all” URL of your Verdaccio instance (i.e. by typing https://<org-domain>/-/all in your browser address bar)? If not, that would likely be the reason why they don’t show up. But if they do appear in the browser, then something else is going on, in which case I would suggest reporting a Bug.

3

Verdaccio does implement the new /-/v1/search endpoint (I get a reply from it), but it returns 0 for us - all our packages are only accessible by authenticated users. We have set up authentication with the .upmconfig.tmol file and I can access packages by adding them directly in manifest.json file, but don’t see them listed.

4

Hi @unnanego,

Are there any error messages in the upm.log or Editor.log files, or in the Unity Editor console?

Do you get any result when you try the same using npm search <your-package-name> --registry=<your-registry> on the command-line, using the same credentials? If you also get no results from npm search but do get results from npm view <your-package-name> --registry=<your-registry>, then it’s more likely either a configuration issue in your Verdaccio setup or a bug in the Verdaccio code, in which case the Verdaccio documentation or the Verdaccio project maintainers/community are more likely to be able to help.

5

Well, somehow it just started working)

1 Like