@uppy/progress-bar no longer available in Yarn?

Running our CI today at work, we get an error message when running yarn install with the following info:

An unexpected error occurred: "https://registry.yarnpkg.com/@uppy/progress-bar/-/progress-bar-2.1.1.tgz: Request failed \"404 Not Found\"".

Navigating to the listed URL does indeed give a 404 response, as well as going to registry.yarnpkg . com/@uppy/progress-bar

Notably, other @uppy packages return non-404 responses when visited, including registry.yarnpkg . com/@uppy/status-bar and registry.yarnpkg . com/@uppy/react.

Has something happened with a recent progress-bar deploy that has caused an issue? Or is progress-bar being removed from the ecosystem? Thanks in advance for any help/insight.

Edit: wanted to also note that we are not explicitly using @uppy/progress-bar in our app, it is being pulled in as a dependency of @uppy/react

Same with NPM just now - was working 30 minutes or so ago on my last build.

Yep, we had a successful build around 2 hours ago, same commit re-processed in CI now fails with the above error

Looks like its a registry problem (on NPM at least). I have another failing package from a different vendor now. FML

NPM is not reporting any incidents. Are you using AWS Amplify by any chance? Issue could be there? Iā€™m getting an extra /-/ in my registry paths.

Everything is working fine when building locally. (same package versions)

We are not, our failures are happening in CircleCI. That said, CircleCI uses AWS for their infrastructure, so perhaps it could be related?

Looks like there is an error being reported now:

1 Like

This issue seems to have resolved itself along with the NPM issue tracker