### New Issue 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). - [x] I can reproduce the issue with the latest versions of [Parse Server](https://github.com/parse-community/parse-server/releases) and the [Parse JS SDK](https://github.com/parse-community/Parse-SDK-JS/releases). <!-- We don't investigate issues for outdated releases. --> ### Issue Description <!-- What is the specific issue? --> Legacy import are in the form of `const Parse = require('parse').Parse`. This can be solved using `export` statement. https://github.com/parse-community/Parse-SDK-JS/blob/cfb25ef322632c4136de3ab416f719f014f66027/src/Parse.ts#L417-L418 <img width="258" alt="Image" src="https://github.com/user-attachments/assets/56b16d01-7c09-4fac-8daf-9f83121a45b6" />
New Issue Checklist
Issue Description
Legacy import are in the form of
const Parse = require('parse').Parse. This can be solved usingexportstatement.Parse-SDK-JS/src/Parse.ts
Lines 417 to 418 in cfb25ef