-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Missmatch with npmjs.com #369
Comments
Thanks for bringing this to our attention, I'm fixing it right now. @DxCx it also looks like the README.md files on npm for each package are extremely minimal and just link to the docs. I think we should change that. |
@helfer |
Haha, I don't remember that, but it sounds like something I would say. Since I don't have a lot of time right now, I hope we can split up the work among a few people. Do you remember who the main authors are for the various packages? |
ok, I think none of these people have made any commits recently. Let's just create an issue and tag it with "help wanted"! |
#373. |
The npm link on graphql.org leads to the graphql-server npm page which references github.com/apollostack/apollo-server as repository which den forwards to github.com/apollographql/graphql-server.
The npm page further uses a readme that seems to be deprecated, saying that one should run
npm install apollo-server
to install and use some code syntax if I'm not mistaken.This problem only became apparent when npm complained because of a peer dependency missmatch, leading to #291 and #243 explaining that this was deprecated and
npm install graphql-server-<variant>
was the correct syntax as also noted in the readme of this repository.All in all the conflicting and deprecated information is really confusing when starting using this lib so I think the information should be updated accordingly.
The text was updated successfully, but these errors were encountered: