parse-community / parse-community/parse-dashboard
Remove graphIQL console and API console
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 3.8k
- Forks
- 1.4k
- PR merge metrics
- No merged PRs in 30d
Description
New Feature / Enhancement Checklist
- I am not disclosing a vulnerability.
- I am not just asking a question.
- I have searched through existing issues.
Current Limitation
Both the graphIQL console and API console add heavy dependencies to this project, bloating node modules out quite a bit. The dashboard is used for managing data of a live Parse Server, being able to write and execute javascript in an editor that has no types, terminal, debugging, etc, is practically useless.
Feature / Enhancement Description
Remove react-ace, graphIQL
Example Use Case
Allows dashboard to be deployed on smaller instances
Alternatives / Workarounds
Remove from package-lock.json and run npm ci`
3rd Party References
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating references to react-ace and GraphiQL, then inspect package-lock.json to identify the dependencies and their use in the dashboard. Run npm ci after the removal; done means both consoles are gone and the unused dependencies no longer inflate the installed modules.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- graphql, javascript, react
- Domain
- frontend, tooling
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100