Remove graphIQL console and API console

[dblythy]

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

parse-community/parse-server#7979

[parse-github-assistant]

Thanks for opening this issue!

• 🎉 We are excited about your ideas for improvement!

[mtrezza]

Well, it may be still the quickest option to execute some JS code on Parse Server. What is the current impact of these features in terms of bloating?

[dblythy]

ace-builds is 50M, graphiql is 10M. Not huge, but they have many subdependancies as well

[mtrezza]

Is there any other impact apart from the additional 60MB?

Unfortunately we don't have any usage statistics. Maybe the leading question is whether we want such a feature in the dashboard at all. If no we can remove it; if yes we could keep it and start an issue about what we want to improve about it. For example, is there a better editor with type checking, auto-complete, etc that could be used instead?

Or how about writing a VSC plugin for Parse Server that allows to easily connect to a (local) Parse Server instance and execute code? That way all the benefits of an IDE come out of the box. #2318