### New Feature / Enhancement Checklist <!-- Check every following box [x] before submitting your issue. Click the "Preview" tab for better readability. Thanks for contributing to Parse Platform! --> - [x] I am not disclosing a [vulnerability](https://github.com/parse-community/parse-server/blob/master/SECURITY.md). - [x] I am not just asking a [question](https://github.com/parse-community/.github/blob/master/SUPPORT.md). - [x] I have searched through [existing issues](https://github.com/parse-community/Parse-SDK-JS/issues?q=is%3Aissue). ### Current Limitation <!-- Which current limitation is the feature or enhancement addressing? --> Follow up of the discussion on #203 Currently, the SDK is imported globally, and the compilers cannot optimize the imports and remove unused code. Firebase have a great explanation https://firebase.googleblog.com/2021/08/the-new-firebase-js-sdk-now-ga.html?m=1 ### Feature / Enhancement Description <!-- What is the concept of the functionality and how should it be implemented? --> This would allow to reduce the compiled client side app by eliminating the unused code. This would also allow to fix #203 by allowing to create instances the Parse library for those who need to interact with multiple Servers. ### Example Use Case <!-- What is an example use case in steps (1. / 2. / 3. / etc.) that describes the functionality? --> ### Alternatives / Workarounds <!-- Which alternatives or workarounds exist currently? --> ### 3rd Party References <!-- Have you seen a similar functionality provided somewhere else? --> https://www.codingame.com/playgrounds/7463/tree-shaking-in-javascript-with-rollup