Parse-dashboard: Dependency on codemirror-graphql branch

[mtrezza]

Make sure these boxes are checked before submitting your issue -- thanks for reporting issues back to Parse Dashboard!

• [x] You're running version >=1.0.23 of Parse Dashboard.
• [x] You're running version >=2.3.2 of Parse Server.
• [x] You've searched through existing issues. Chances are that your issue has been reported or resolved before.

Environment Setup

Parse Dashboard has a dependency on a personal branch:
https://github.com/parse-community/parse-dashboard/blob/faf8d2dc739625f183c8b548b8a3d09b079276a7/package.json#L41

The branch is not maintained.

Solution

The dependency should point to the original repository or Parse should to maintain its own fork if necessary.

[Nes-si]

Seems like this issue makes it impossible using parse-dashboard in project if you have new npm version.
npm i finishes with an error:

npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! Found: [email protected]
npm ERR! node_modules/graphql
npm ERR!   graphql@"15.4.0" from [email protected]
npm ERR!   node_modules/parse-server
npm ERR!     parse-server@"^4.5.0" from the root project
npm ERR!   peer graphql@"^14.0.0 || ^15.0.0" from [email protected]
npm ERR!   node_modules/graphql-language-service-parser
npm ERR!     graphql-language-service-parser@"^1.0.18" from [email protected]
npm ERR!     node_modules/codemirror-graphql
npm ERR!       codemirror-graphql@"github:timsuchanek/codemirror-graphql#details-fix" from [email protected]
npm ERR!       node_modules/parse-dashboard
npm ERR!         parse-dashboard@"^2.1.0" from the root project
npm ERR!     graphql-language-service-parser@"^1.2.2" from [email protected]
npm ERR!     node_modules/codemirror-graphql/node_modules/graphql-language-service-interface
npm ERR!       graphql-language-service-interface@"^1.0.18" from [email protected]
npm ERR!       node_modules/codemirror-graphql
npm ERR!         codemirror-graphql@"github:timsuchanek/codemirror-graphql#details-fix" from [email protected]
npm ERR!         node_modules/parse-dashboard
npm ERR!   4 more (graphql-language-service-types, apollo-link, ...)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer graphql@"^0.10.0 || ^0.11.0 || ^0.12.0 || ^0.13.0" from [email protected]
npm ERR! node_modules/codemirror-graphql/node_modules/graphql-language-service-interface
npm ERR!   graphql-language-service-interface@"^1.0.18" from [email protected]
npm ERR!   node_modules/codemirror-graphql
npm ERR!     codemirror-graphql@"github:timsuchanek/codemirror-graphql#details-fix" from [email protected]
npm ERR!     node_modules/parse-dashboard
npm ERR!       parse-dashboard@"^2.1.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.

[beppemac]

I solved by deleting the node_modules folder and package-lock.json file and finally run npm i.

[Nes-si]

I solved by deleting the node_modules folder and package-lock.json file and finally run npm i.

It's not a solution. The problem deals with new npm version (v7) which installs peer-dependencies. You obviously used npm v6 or earlier.

[moneppo]

Originally I got stuck believing that --legacy-peer-deps would work until this package was upgraded. I was able to downgrade to [email protected] to work around this issue.

[ritterb82]

Same problem. Can't run parse dashboard with latest npm version.

[ritterb82]

Originally I got stuck believing that --legacy-peer-deps would work until this package was upgraded. I was able to downgrade to [email protected] to work around this issue.

Just wanted to point out the version should be 6.14.11. ( not 16.14.11 )

[architectcodes]

Just chipping in to let the maintainers know that this makes for a pretty disappointing first impression when getting started with Parse Server and the stable version of Node.js and npm 😬

[mtrezza]

Thanks everyone for pinning this down. I think we should add a compatibility table just like we have for Parse Server and ideally add CI tests to detect such incompatibilities.

Would anyone want to give it a try?

[mtrezza]

For convenience, this is how to downgrade from npm 7 to 6 on macOS using brew:

$ brew install node@14
$ brew unlink node
$ brew link --overwrite --force node@14

[stage88]

Would it work if we upgrade dependancy graphql-playground-react. It seems to be the one which breaks the install. See my comment here https://github.com/parse-community/parse-server/issues/7090#issuecomment-789659616

I dont have much experience with graphql, but I can try tomorrow. Its getting late here in AUS.

[mtrezza]

Thanks for trying this out. If we can't find a solution, we may have to either fork and maintain our own to bypass the prepare script or remove the codemirror / playground all together. The original package I referenced in this issue has been deprecated and moved into a mono-repo, but I also couldn't get to install that mono-repo.

[elijahjcobb]

Can confirm this is still an issue with the latest versions of everything.

[rakuemoevi]

I can confirm i'm not able to deploy to heroku getting error message:
/usr/bin/git ls-remote -h -t ssh://[email protected]/timsuchanek/codemirror-graphql.git
remote: npm ERR!
remote: npm ERR! Host key verification failed.
remote: npm ERR! fatal: Could not read from remote repository.
I'm using:
"node": "13.14.0" and "npm": "6.14.4"

[architectcodes]

Node 14 and lower is not compatible with Apple Silicon chips (see https://github.com/nodejs/node/issues/36161). It’s a deadlock – Parse Dashboard cannot be used on late 2020 Macs and newer 😱

[mtrezza]

I would think the dashboard runs on Node 15 too, have you tried? Is this related to this issue or something separate?

[architectcodes]

Node 15 ships with npm 7, which refuses to install parse-dashboard.

If you’re suggesting we can downgrade npm to v6 on Node 15, I didn’t try that, because it’s a very painful workflow that I wouldn’t want to introduce. Everyone on the team would need to remember to switch to a non-default version of npm after installing Node.