Install error on npm 7

[tristanyi]

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

• You're running version >=1.0.23 of Parse Dashboard.

• You're running version >=2.3.2 of Parse Server.

• You've searched through existing issues. Chances are that your issue has been reported or resolved before.

Environment Setup

ubuntu18
node 14
npm 6

Steps to reproduce

npm ERR! code ELIFECYCLE
npm ERR! syscall spawn
npm ERR! file sh
npm ERR! errno ENOENT
npm ERR! core-js@2.6.12 postinstall: node -e "try{require('./postinstall')}catch(e){}"
npm ERR! spawn ENOENT
npm ERR!
npm ERR! Failed at the core-js@2.6.12 postinstall script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

Logs/Trace

Note: If you get a browser JS error please run npm run dev. This will provide source maps and a much more useful stack trace.

[elrumo]

I'm also having issues installing parse-server from NPM. I get dependancy errors and I can't install it

[siempay]

I am having same problem right now !

[dplewis]

Can you try ignore scripts flag on install?

npm install --ignore-scripts

[siempay]

Just tried it and it failed too

npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! Found: graphql@14.6.0
npm ERR! node_modules/parse-dashboard/node_modules/graphql
npm ERR!   graphql@"14.6.0" from parse-dashboard@2.1.0
npm ERR!   node_modules/parse-dashboard
npm ERR!     parse-dashboard@"*" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer graphql@"^0.11.0 || ^0.12.0 || ^0.13.0" from graphql-import@0.4.5
npm ERR! node_modules/parse-dashboard/node_modules/codemirror-graphql/node_modules/graphql-language-service-interface/node_modules/graphql-import
npm ERR!   graphql-import@"^0.4.4" from graphql-config@2.0.1
npm ERR!   node_modules/parse-dashboard/node_modules/codemirror-graphql/node_modules/graphql-language-service-interface/node_modules/graphql-config
npm ERR!     graphql-config@"2.0.1" from graphql-language-service-interface@1.3.2
npm ERR!     node_modules/parse-dashboard/node_modules/codemirror-graphql/node_modules/graphql-language-service-interface
npm ERR!       graphql-language-service-interface@"^1.0.18" from codemirror-graphql@0.6.12
npm ERR!       node_modules/parse-dashboard/node_modules/codemirror-graphql
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 /Users/brahimelmssilha/.npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:

[dblythy]

I too, get the same error as @siempay.

Replication:

1. Create a package.json file in a new directory with the contents:

{
  "dependencies": {
    "parse-dashboard": "^2.1.0",
    "parse-server": "^4.5.0"
  }
}

2. run npm install, or npm install --ignore-scripts

[dblythy]

As previously discussed, this only happens on the latest version of npm on certain devices. I solved by downgrading npm to 6.14.10.

[amankch]

resolved with yarn add parse-dashboard --save. Maybe it will help others. graphql warning still there.

[0biWanKenobi]

Hi all,

this still happens. Current npm LTS is 7.20.6, and for most users it's not feasible to downgrade.. Could this problem be fixed?

[mtrezza]

There is another issue (which I can't find now) that has been opened regarding this. It seems to be an issue with the graphql dependency and npm 7 compatibility. We have an open PR to upgrade the dependency, which probably will solve this issue. The PR is a major version upgrade, so it requires some refactoring, that's why it is not merged yet. It would be great if someone could look into this.

[0biWanKenobi]

There is another issue [...]

Probably #1633 ? Yeah I've seen the PR, and I even used that branch locally to ease my development, seems to work - of course it would need rigorous testing though. I mainly commented here in hopes the problem gets picked up, as someone mentioned it's really a bad first hands-on experience for a developer; I know it has been for me. I struggled a lot and ended up finding a fork on npmjs that ""works"", but if my company hadn't decided to use Parse, I know I'd have jumped ship to Firebase.

[mtrezza]

@0biWanKenobi Thanks for sharing your concern. I agree that this is something we should fix ASAP, also since npm 6 is already considered "legacy" by node.

Would you be willing to take a look at the PR and try to update to the next version of the GraphQL dependency?

As far as I remember, the alternative solution would be to remove the GraphQL playground from the dashboard, because I think that is the only feature that requires the GraphQL package. That would of course be a drastic step for people who use that feature, but if we can't get it to work otherwise, it may be the only way forward.

[0biWanKenobi]

Would you be willing to take a look at the PR and try to update to the next version of the GraphQL dependency?

Yeah ideally I'd love to, but work hours don't leave much free time 😞 If someone can pick this up, it would be awesome