Skip to content

parse-dashboard: command not found #1248

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

Closed
1 task done
Treverr opened this issue Aug 26, 2019 · 6 comments
Closed
1 task done

parse-dashboard: command not found #1248

Treverr opened this issue Aug 26, 2019 · 6 comments
Labels
state:wont-fix Won’t be fixed with a clearly stated reason

Comments

@Treverr
Copy link

Treverr commented Aug 26, 2019

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

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

  • [NA] 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

Steps to reproduce

npm install -g parse-dashboard
parse-dashboard --config parseDash.json

Logs/Trace

npm install -g parse-dashboard
npm WARN deprecated [email protected]: core-js@<2.6.8 is no longer maintained. Please, upgrade to core-js@3 or at least to actual version of core-js@2.
npm WARN deprecated [email protected]: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
npm WARN deprecated [email protected]: This module has moved and is now available at @hapi/boom. Please update your dependencies as this version is no longer maintained an may contain bugs and security issues.
npm WARN deprecated [email protected]: This module has moved and is now available at @hapi/hoek. Please update your dependencies as this version is no longer maintained an may contain bugs and security issues.
npm WARN deprecated [email protected]: Switch to the bfj package for fixes and new features!
/home/trever/.npm-global/bin/parse-dashboard -> /home/trever/.npm-global/lib/node_modules/parse-dashboard/bin/parse-dashboard
npm WARN [email protected] requires a peer of graphql@^0.10.0 || ^0.11.0 || ^0.12.0 but none is installed. You must install peer dependencies yourself.
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.
npm WARN [email protected] requires a peer of graphql@^0.11.0 || ^0.12.0 || ^0.13.0 but none is installed. You must install peer dependencies yourself.
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.
npm WARN [email protected] requires a peer of graphql@^0.11.0 || ^0.12.0 || ^0.13.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of graphql@^0.6.0 || ^0.7.0 || ^0.8.0-b || ^0.9.0 || ^0.10.0 || ^0.11.0 || ^0.12.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of react@>=15.5 <16 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of react-dom@>=15.5 <16 but none is installed. You must install peer dependencies yourself.

  • [email protected]
    updated 1 package in 8.355s
    trever@server:~$ parse-dashboard --config parseDash.json
    parse-dashboard: command not found
@davimacedo
Copy link
Member

Can you please send us more details about your OS, Node.js version and Npm version? Tks.

@Treverr
Copy link
Author

Treverr commented Aug 26, 2019

OS: Ubuntu 18.04.2 LTS (GNU/Linux 4.15.0-58-generic x86_64)
Node.js: v8.10.0
NPM: 6.11.2

@davimacedo
Copy link
Member

Can you try with node.js >= 10?

@Treverr
Copy link
Author

Treverr commented Aug 26, 2019

I attempted this and still am getting the same issue.

@davimacedo
Copy link
Member

It seems that npm is not properly installed in your OS since you are installing a global package and the command is not recognized. Do you mind to take a look in this article here?

@stale
Copy link

stale bot commented Oct 11, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the state:wont-fix Won’t be fixed with a clearly stated reason label Oct 11, 2019
@stale stale bot closed this as completed Oct 18, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
state:wont-fix Won’t be fixed with a clearly stated reason
Projects
None yet
Development

No branches or pull requests

2 participants