Verdaccio Scoped Packages fail, but unscoped packages working?

Unity Engine
1

Unity 2018.4.0f1

I have set up a local test Verdaccio, and have been trying to use scoped packages to obtain our packages in Unity but they can’t be found. However unscoped packages succeed. I can verify that all packages exist in the scope (or unscope) expected on the file system.

Fails

// Package is scoped
//
// @com.company/package.name
//
// Unity fails to import this package.
{
  "scopedRegistries": [
    {
      "name": "packages",
      "url": "http://localhost:myport",
      "scopes": [
        "com.company"
      ]
    }
  ],
  "dependencies": {
    "com.company.package.name": "1.2.3",
    ...
  }
}

Succeeds

// Package is unscoped
//
// com.company.package.name
//
// Unity succeeds at importing this package.
// however, I MUST use the fully qualified package name in the scopes array
//
{
  "scopedRegistries": [
    {
      "name": "packages",
      "url": "http://localhost:myport",
      "scopes": [
        "com.company.package.name"
      ]
    }
  ],
  "dependencies": {
    "com.company.package.name": "1.2.3",
    ...
  }
}

Is this expected behavior? Is this a bug? Is there something I’m doing wrong?

Edit : Can verify that the scoped package is found in the browser, but not by Unity at this address…

http : //localhost:myport/@com.company/package.name

2

Hello,
Sorry to hear you have issues using the scoped registries feature.
Unfortunately, your issue arises because scoped registries are only available from 2019.1 and upward.

If you look in the Unity manual at Unity - Manual: Scoped registries, you can see that this feature is not available in 2018.4 by pressing the “Version” dropdown found in the top-left corner of the page, right below the page header.

1 Like
3

Thanks @cassandraL , I appreciate the clarification. As long as unscoped packages work in 2018, at the very least we could use those for internal tools until we are assured of migrating the entire team to 2019