Closed baron1405 closed 5 years ago
@baron1405,
This likely means you are using a custom registry and that registry needs to import the new packages that ember-data
depends upon.
You can see that the -build-infra
package is indeed published correctly by using npm view @ember-data/-build-infra
Apparently others have hit this as well - verdaccio/verdaccio#1429. What I do not understand is why all of a sudden starting in 3.11.0 my nexus proxy-based repository is failing to find a single dependency whereas it has been working fine for years with ember. The only thing I can think of that is new is the leading dash in the package name.
Talking directly to the yarn or npm repos works so it must be something related to the npm plugin for Nexus 2.
Attempting to upgrade ember-data from 3.10.0 to 3.11.2, I get the following error:
All other ember packages (e.g. ember-cli, ember-source) update successfully. I have verified that the package is listed in the npm registry. I have tried removing my yarn.lock and node_modules directory to start fresh but the problem still occurs.
Environment: CentOS 7.6 Yarn 1.17.3