-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Dependency on codemirror-graphql branch #1633
Comments
Seems like this issue makes it impossible using parse-dashboard in project if you have new npm version.
|
I solved by deleting the |
It's not a solution. The problem deals with new npm version (v7) which installs peer-dependencies. You obviously used npm v6 or earlier. |
Originally I got stuck believing that |
Same problem. Can't run parse dashboard with latest npm version. |
Just wanted to point out the version should be 6.14.11. ( not 16.14.11 ) |
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 😬 |
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? |
For convenience, this is how to downgrade from npm 7 to 6 on macOS using brew:
|
Would it work if we upgrade dependancy I dont have much experience with graphql, but I can try tomorrow. Its getting late here in AUS. |
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. |
Can confirm this is still an issue with the latest versions of everything. |
I can confirm i'm not able to deploy to heroku getting error message: |
Node 14 and lower is not compatible with Apple Silicon chips (see nodejs/node#36161). It’s a deadlock – Parse Dashboard cannot be used on late 2020 Macs and newer 😱 |
I would think the dashboard runs on Node 15 too, have you tried? Is this related to this issue or something separate? |
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. |
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. |
Don't close it please. |
Isn't that also true for Parse Server? I think it currently also doesn't install with npm 7 due to dependency issues. Can anyone try and confirm this? |
No problem installing Parse Server with npm 7 but no way for Parse Dashboard even with the lagacy peer deps or the force option. With regret, we are forced to consider discontinuing the use of this package. It's sad, especially just for one dependency... |
Closed via #1807 |
Make sure these boxes are checked before submitting your issue -- thanks for reporting issues back to Parse Dashboard!
Environment Setup
Parse Dashboard has a dependency on a personal branch:
parse-dashboard/package.json
Line 41 in faf8d2d
The branch is not maintained.
Solution
The dependency should point to the original repository or Parse should to maintain its own fork if necessary.
The text was updated successfully, but these errors were encountered: