Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Dependency @wry/caches / other @wry packages 404 now on NPM #12197

Closed
camsjams opened this issue Dec 8, 2024 · 5 comments
Closed

Dependency @wry/caches / other @wry packages 404 now on NPM #12197

camsjams opened this issue Dec 8, 2024 · 5 comments

Comments

@camsjams
Copy link

camsjams commented Dec 8, 2024

Issue Description

It looks like the package @wry/caches was removed or made private.

Same is true for the other @wry packages it seems:

error An unexpected error occurred: "https://registry.npmjs.org/@wry/caches/-/caches-1.0.1.tgz: 
Request failed \"404 Not Found\"".

I'm not familiar with the owners of this package, but it is currently breaking builds:
image

Link to Reproduction

npm install apollo client

Reproduction Steps

  1. Install apollo client
  2. npm install @apollo/client
  3. yard add @apollo/client

@apollo/client version

3.9.7+, really all versions with @wry/caches as a dependency

@camsjams camsjams changed the title Dependency @wry/caches 404s now on NPM Dependency @wry/caches / other @wry packages 404 now on NPM Dec 8, 2024
@camsjams
Copy link
Author

camsjams commented Dec 8, 2024

I've also added a note on this repo:
benjamn/wryware#645

@camsjams
Copy link
Author

camsjams commented Dec 8, 2024

And they're back - someone must have fixed. Thanks!

@camsjams camsjams closed this as completed Dec 8, 2024
Copy link
Contributor

github-actions bot commented Dec 8, 2024

Do you have any feedback for the maintainers? Please tell us by taking a one-minute survey. Your responses will help us understand Apollo Client usage and allow us to serve you better.

@phryneas
Copy link
Member

phryneas commented Dec 9, 2024

Npm had a planned outage yesterday: https://status.npmjs.org/incidents/px35z3dmcjgm, that probably explains it.

Please always check the npm status page

Copy link
Contributor

github-actions bot commented Jan 9, 2025

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
For general questions, we recommend using our Community Forum or Stack Overflow.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jan 9, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants