-
-
Notifications
You must be signed in to change notification settings - Fork 133
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
Package rename #68
Labels
Comments
I've found this package to be compatible with: |
|
All done 🎉 I just published Here is the deprecation warning everyone sees when attempting to install The Github short URL links to this issue. |
jaydenseric
added a commit
to jaydenseric/graphql-multipart-request-spec
that referenced
this issue
Sep 18, 2018
…-server as deprecated. See jaydenseric/graphql-upload#68.
This was referenced Jun 15, 2019
KushalKatta
added a commit
to KushalKatta/graphql-yoga
that referenced
this issue
Nov 3, 2019
apollo-upload-server is deprecated. here is the link: jaydenseric/graphql-upload#68 (comment)
krasivyy3954
added a commit
to krasivyy3954/react-graphql-upload
that referenced
this issue
Jan 6, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It is time to drop
apollo
from theapollo-upload-server
package name as this package is also useful for non-Apollo GraphQL servers and clients.Anyone have any tips for renaming a package? I have never done it before and it seems like an inherently disruptive thing to do.
I'm thinking:
express-graphql
.package.json
and anywhere else the name appears.I'll think about it for a bit before doing it 😅
The text was updated successfully, but these errors were encountered: