Migrate to mono-repository

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

We currently have several JS repositories to manage (Parse Server, Parse Dashboard, Parse JS SDK, Docs, Push Adapter, Node APN, etc), which make it harder to create/maintain features requiring changes in multiple packages. It also requires extra effort to create new releases when we need to update all the packages bottom up.

Feature / Enhancement Description

Combine all JS repositories into a single monorepository (perhaps using lerna).

Example Use Case

• Release all JS packages at once
• Single PR involving multiple packages
• Requiring docs and dashboard changes in the same PR of a new feature to the Parse Server
• Track the docs we had in place at the moment we released each Parse Server version

Alternatives / Workarounds

• We will have to decide if we will create a new repo and move all current repos to the new one or if we will choose one current repo to move the others in
• We can first try with two or three repos and then move the others
• We can choose to continue as is now but at least try to automate the release of multilpe repos at once

3rd Party References

Next.js
Apollo GraphQL Server
Parse React

Review the current Parse Server, Dashboard, JS SDK, Docs, Push Adapter, and Node APN repositories first, then compare the two- or three-repository pilot with a full migration and the Lerna approach. Done means an agreed repository layout and a workable way to release all packages together while preserving versioned documentation.