Hi everyone! I'm a front-end engineer, and I could really use some help here. Recently, we upgraded our entire React application from version 16 to 18 and moved from Node.js 12 to 18 as well. However, ever since this upgrade, I'm running into recurring errors while publishing builds. It seems some versions of packages in our JFrog NPM private registry are either missing or outdated. I've checked Artifactory, and it confirms that those versions aren't available. How can I resolve this issue?
4 Answers
If those packages are from a private repo, you might need to reach out to your JFrog admin or the team responsible for those libraries. Are you getting 401 or 403 errors when you try to access them?
Unless you have elevated privileges, tracking remote repositories in Artifactory is usually managed by admins. If you're not tracking a remote repo, you might need to upload the missing packages manually. I suggest emailing the relevant team with something like this:
Subject: Missing Packages or Versions in Private NPM Registry After React/Node Upgrade.
In your email, explain that you’ve recently upgraded your project and are facing issues with missing packages in the JFrog NPM registry. Include specific requests for them to investigate and help ensure the necessary versions are available moving forward. If you need specific error logs, offer to share them.
The problem is we don’t actually have a dedicated DevOps team anymore since they were disbanded after the initial setup, so we’re pretty much on our own.
Did you also upgrade Yarn when you made those changes? I remember there being some compatibility issues with certain versions.
We’re using Yarn for publishing, and our version is still 1.22.22. So we didn’t upgrade Yarn itself.
No, for the artifactory repo, I'm getting a 200 OK status.