Express-graphql: Latest express-graphql is not working with the latest graphql

Created on 7 Sep 2018  路  17Comments  路  Source: graphql/express-graphql

Latest express-graphql isnot working with the latest graphql:

npm install express-graphql@latest --save
npm WARN [email protected] requires a peer of graphql@^0.10.0 || ^0.11.0 || ^0.12.0 || ^0.13.0 but none is installed. You must install peer dependencies yourself.

package.json:

  "dependencies": {
    "express-graphql": "^0.6.12",
    "graphql": "^14.0.2",
  }

Most helpful comment

Guys.
What I have done is gone through each warning and tried to install them.
npm WARN [email protected] requires a peer of rxjs@^6.5.0
so I did sudo npm install rxjs then I again got warning with
..requires a peer of graphql@^14.4.1 so I guess the graphql is not installed in my system so I did
sudo npm install graphql which respond
npm WARN [email protected] No repository field. then again
sudo npm install rxjs which output
npm WARN [email protected] No repository field. then finally I ran
'sudo npm install graphql-express'
npm WARN [email protected] No repository field.

That's it.

All 17 comments

@speller Thanks for reporting 馃憤
I'm currently working on it and master already supports 14.0.0: 5c04d1838020f691cc3dc9b098635593a75e7a1d
But I can't publish new NPM package since NPM revoked all keys:
https://blog.npmjs.org/post/175824896885/incident-report-npm-inc-operations-incident-of

I already contact Facebook engineers to set up a new key and I expect it to be done in the next few days.
I will try to keep you updated.

hey @IvanGoncharov when it does get pushed out we could just run:
npm install express-graphql@latest --save

and it should work correct?

+1, any new on this?

@IvanGoncharov Let me see who the POC to get you added back on npm is. In the meantime I can cut a release sometime this week. Is there anything else that we want to do before cutting a release?

@wizyoua Yes.

Let me see who the POC to get you added back on npm is

@AGS- Thanks 馃憤 Can you please, also update keys in graphql-js and other repos?

Is there anything else that we want to do before cutting a release?

I think it's ready. I just updated deps and switched to GraphiQL 0.12.0(BTW, big thanks for releasing it 馃帀).

@IvanGoncharov the repo was updated but the version remains the same 0.6.12, shouldn't it be bumped (e.g. 0.6.13) and published on npm? Running yarn add express-graphql still installs the v0.6.12

@CoericK, the version is bumped when the package is published to npm, not before that. Hopefully, we will be able to make a new release sometime this week.

@AGS- Ah makes sense! Thanks for mention it!

+1, any updates?

+1, can you please update the npm repo. Keep up the great work

+1, any updates??

@erayhanoglu @flasaracina Sorry for the delay, this issue is still blocked because I'm doesn't have NPM keys yet, but @AGS- doing a great job trying to resolve this issue.
I will keep you updated and hopefully release soon.

So still no updates?

+1

Just published a new version to npm.

Thanks guys!

Guys.
What I have done is gone through each warning and tried to install them.
npm WARN [email protected] requires a peer of rxjs@^6.5.0
so I did sudo npm install rxjs then I again got warning with
..requires a peer of graphql@^14.4.1 so I guess the graphql is not installed in my system so I did
sudo npm install graphql which respond
npm WARN [email protected] No repository field. then again
sudo npm install rxjs which output
npm WARN [email protected] No repository field. then finally I ran
'sudo npm install graphql-express'
npm WARN [email protected] No repository field.

That's it.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

mkermani144 picture mkermani144  路  5Comments

arealmaas picture arealmaas  路  4Comments

m-diiorio picture m-diiorio  路  4Comments

macin40 picture macin40  路  4Comments

kaareal picture kaareal  路  3Comments