Closed LilMoke closed 3 years ago
The issue description lacks essential information, as the form has not been filled out properly. However, given your description I suggest:
package-lock.js
and node_modules
are deleted before rebuilding the node app.I'm closing this as it does not seem to be a Parse Server issue.
For help with Parse Server, here are some resources you can try:
Feel free to comment if you have any questions and we can re-open this issue.
Hi, I`m getting the same error when I deployed application using docker hub
@mobappsbr Feel free to copy/paste a filled out issue template as comment here and we can re-open this issue.
We use the docker hub infrastructure for our deployment process. So 2 days ago, without changing anything in our package.json in a new release of the application the deployment process started to fail and is no longer running due to the GraphQL library.
Server
4.4.0 and 4.3.0
Linux
DOCKERHUB
Database
Client
KernelVersion: 4.4.0-1060-aws
Arch: amd64
BuildTime: 2020-03-11T01:24:30.000000000+00:00
ApiVersion: 1.40
Platform: {u'Name': u'Docker Engine - Community'}
Version: 19.03.8
MinAPIVersion: 1.12
GitCommit: afacb8b7f0
Os: linux
GoVersion: go1.12.17
Starting build of index.docker.io/....
Step 1/13 : FROM node:latest
---> 6c5fc80a4d2b
Step 2/13 : RUN mkdir parse
---> Running in a7c452d25f1c
Removing intermediate container a7c452d25f1c
---> e90185469f37
Step 3/13 : ADD . /parse
---> e33577141e5e
Step 4/13 : WORKDIR /parse
---> Running in 4aa813a631c2
Removing intermediate container 4aa813a631c2
---> efad961677fd
Step 5/13 : RUN npm install
---> Running in 7a75beee3f4d
[91mnpm[0m
[91m [0m
[91mWARN[0m
[91m [0m
[91mERESOLVE[0m
[91m overriding peer dependency
[0m
[91mnpm[0m
[91m [0m
[91mWARN[0m
[91m Found: graphql@15.3.0
[0m
[91mnpm[0m
[91m [0m
[91mWARN[0m
[91m node_modules/graphql
[0m
[91mnpm[0m
[91m [0m
[91mWARN[0m
[91m graphql@"15.3.0" from parse-server@4.4.0
[0m
[91mnpm[0m
[91m [0m
[91mWARN[0m
[91m node_modules/parse-server
[0m
[91mnpm WARN parse-server@"4.4.0" from the root project
npm WARN 4 more (@graphql-tools/links, @graphql-tools/stitch, ...)
npm WARN
npm WARN Could not resolve dependency:
npm WARN peer graphql@"^0.5.0 || ^0.6.0 || ^0.7.0 || ^0.8.0-b || ^0.9.0 || ^0.10.0 || ^0.11.0 || ^0.12.0 || ^0.13.0 || ^14.0.0" from graphql-relay@0.6.0
npm WARN node_modules/graphql-relay
npm WARN graphql-relay@"0.6.0" from parse-server@4.4.0
npm WARN node_modules/parse-server
[0m
[91mnpm[0m
[91m [0m
[91mnotice[0m
[91m
[0m
[91mnpm[0m
[91m [0m
[91mnotice[0m
[91m New patch version of npm available! 7.0.8 -> 7.0.10
[0m
[91mnpm[0m
[91m [0m
[91mnotice[0m
[91m Changelog: <https://github.com/npm/cli/releases/tag/v7.0.10>
[0m
[91mnpm[0m
[91m [0m
[91mnotice[0m
[91m Run `npm install -g npm@7.0.10` to update!
[0m
[91mnpm[0m
[91m [0m
[91mnotice[0m
[91m
[0m
[91mnpm[0m
[91m [0m
[91mERR![0m
[91m [0m
[91mcode[0m
[91m ERESOLVE
[0m
[91mnpm[0m
[91m [0m
[91mERR![0m
[91m [0m
[91mERESOLVE[0m
[91m unable to resolve dependency tree
[0m
[91mnpm[0m
[91m [0m
[91mERR![0m
[91m
[0m
[91mnpm[0m
[91m [0m
[91mERR![0m
[91m Found: graphql@15.3.0
[0m
[91mnpm[0m
[91m [0m
[91mERR! node_modules/graphql
npm[0m
[91m ERR! graphql@"15.3.0" from parse-server@4.4.0
npm ERR! node_modules/parse-server
npm ERR![0m
[91m parse-server@"4.4.0" from the root project
npm ERR! peer graphql@"^14.0.0 || ^15.0.0" from @graphql-tools/links@6.2.4
npm ERR! node_modules/@graphql-tools/links
npm ERR! @graphql-tools/links@"6.2.4" from parse-server@4.4.0
npm ERR! node_modules/parse-server
npm ERR! parse-server@"4.4.0" from the root project
npm ERR! 3 more (@graphql-tools/stitch, @graphql-tools/utils, apollo-server-express)
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer graphql@"^0.10.5 || ^0.11.3 || ^0.12.0 || ^0.13.0 || ^14.0.0" from graphql-subscriptions@1.1.0
npm ERR! node_modules/apollo-server-express/node_modules/graphql-subscriptions
npm ERR! graphql-subscriptions@"^1.0.0" from apollo-server-express@2.18.2
npm ERR! node_modules/apollo-server-express
npm ERR! apollo-server-express@"2.18.2" from parse-server@4.4.0
npm ERR! node_modules/parse-server
npm ERR! parse-server@"4.4.0" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR! See /root/.npm/eresolve-report.txt for a full report.
[0m
[91m
npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2020-11-11T01_30_42_068Z-debug.log
[0m
Removing intermediate container 7a75beee3f4d
The command '/bin/sh -c npm install' returned a non-zero code: 1
Our package.json:
{
“name”: “Server”,
“version”: “1.0.0”,
“description”: “Server”,
“main”: “index.js”,
“license”: “MIT”,
“dependencies”: {
“@babel/runtime”: “7.4.5”,
“bcryptjs”: “2.3.0”,
“body-parser”: “1.19.0”,
“commander”: “2.20.0”,
“connect-flash”: “0.1.1”,
“cookie-session”: “2.0.0-beta.3”,
“cors”: “^2.8.5”,
“create-react-class”: “15.6.3”,
“crypto-js”: “^3.1.9-1”,
“csurf”: “1.10.0”,
“dotenv”: “^8.1.0”,
“express”: “^4.17.1”,
“history”: “4.9.0”,
“immutable”: “3.8.1”,
“immutable-devtools”: “0.1.3”,
“js-beautify”: “1.10.0”,
“json-file-plus”: “3.2.0”,
“kerberos”: “~0.0.x”,
“migrate-mongo”: “6.0.1”,
“mocha”: “^6.2.0”,
“moip-sdk-node”: “^1.2.1”,
“node-cache”: “^4.2.0”,
“node-schedule”: “1.2.5”,
“nodemailer”: “^4.4.1”,
“package-json”: “6.1.0”,
“parse”: “^1.8.5”,
“parse-server”: “4.4.0”,
“parse-server-mailgun”: “2.4.15”,
“passport”: “0.4.0”,
“passport-local”: “1.0.0”,
“prismjs”: “1.16.0”,
“prop-types”: “15.7.2”,
“query-string”: “6.5.0”,
“react”: “16.8.6”,
“react-dnd”: “7.4.5”,
“react-dnd-html5-backend”: “7.4.4”,
“react-dom”: “16.8.6”,
“react-helmet”: “5.2.1”,
“react-router”: “4.4.0-beta.8”,
“react-router-dom”: “4.4.0-beta.8”
},
“scripts”: {
“start”: “node index.js”,
“test”: “mocha -b --timeout 10000”
},
“engines”: {
“node”: “12.3.1”
},
“devDependencies”: {
“eslint”: “^6.4.0”,
“eslint-config-airbnb-base”: “^14.0.0”,
“eslint-plugin-import”: “^2.18.2”
}
}
@mobappsbr, as I commented above, did you take a look at this npm issue?
I am having the same problem with the dependency of graphql on Parse-Server 4.4.0 when trying to push my code changes to Heroku and rebuilding the Node app.
For reference, @LilMoke confirmed that downgrading node worked in their case:
Wow, yes, I used 14.13.1 and my app deploys fine. No errors!
Good to know. Will test it. Thanks!
You may also want to try upgrading npm
to the latest version, I think the bug described in the issue should have been fixed already.
New Issue Checklist
Issue Description
Steps to reproduce
Actual Outcome
Expected Outcome
Environment
Server
4.0.3
FILL_THIS_OUT
Heroku
Database
MongoDB
latest
remote
Client
latest
latest
Logs
-----> Installing dependencies Installing node modules (package.json) npm ERR! code ERESOLVE npm ERR! ERESOLVE unable to resolve dependency tree npm ERR! npm ERR! Found: graphql@15.1.0 npm ERR! node_modules/parse-server/node_modules/graphql npm ERR! graphql@"15.1.0" from parse-server@4.3.0 npm ERR! node_modules/parse-server npm ERR! parse-server@"^4.3.0" from the root project npm ERR! npm ERR! Could not resolve dependency: npm ERR! peer graphql@"^0.10.0 || ^0.11.0 || ^0.12.0 || ^0.13.1 || ^14.0.2" from subscriptions-transport-ws@0.9.16 npm ERR! node_modules/parse-server/node_modules/subscriptions-transport-ws npm ERR! subscriptions-transport-ws@"0.9.16" from parse-server@4.3.0 npm ERR! node_modules/parse-server npm ERR! parse-server@"^4.3.0" from the root project npm ERR! npm ERR! Fix the upstream dependency conflict, or retry npm ERR! this command with --force, or --legacy-peer-deps npm ERR! to accept an incorrect (and potentially broken) dependency resolution. npm ERR! npm ERR! See /tmp/npmcache.ofuvH/eresolve-report.txt for a full report.
-----> Build failed
I just performed a minor update to our app, nothing related to parse. But when we deployed it to the server it started giving the above build error.
I could not find an exact post, but I did see issues referencing some of the same information.
Is this a known issues?
Is there a fix/worekaround?
We did go change it back to 4.0.2, which is what I believe it was before today but it still fails with the same error.
Would you be able to advise me os this issue? It really has me stumped.