feat: Add vite

[dblythy]

Pull Request

• Report security issues confidentially.
• Any contribution is under this license.
• Link this pull request to an issue.

Issue

Closes: #2410

Approach

Vite is more modern than webpack, so approaching building files with vite. Testing will still be needed

Tasks

• Add tests
• Add changes to documentation (guides, repository pages, code comments)

[parse-github-assistant]

I will reformat the title to use the proper commit message syntax.

[parse-github-assistant]

Thanks for opening this pull request!

[dplewis]

Nice! Need some help? I'm interested in seeing how this would work with tree shaking.

[dblythy]

@dplewis I think the challenge here is that Vite might/webpack not be compatible with CJS. Any thoughts?

[dplewis]

I’m not familiar with vite but I see you have a umd bundle in your output, you should be able to output cjs. By compatibility are you referring to the input as cjs? We can change that

[dblythy]

Just having some issues getting some of the browser apis (crypto etc) to polyfill to node. seems to be coming along well though

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.00%. Comparing base (a021d20) to head (a19b99f).
⚠️ Report is 222 commits behind head on alpha.

Additional details and impacted files

@@            Coverage Diff            @@
##             alpha     #2425   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           64        64           
  Lines         6256      6232   -24     
  Branches      1476      1477    +1     
=========================================
- Hits          6256      6232   -24     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[dblythy]

@dplewis everything seems to be working fine except for react native crypto. Any tips would be appreciated 😊

[dplewis]

@dblythy I think we should replace crypto-js and react-native-crypto-js with react-native-quick-crypto and node:crypto. crypto-js is deprecated. On the react-native build you can override crypto with quick-crypto since it built as a drop in replacement and is well maintained.

If we use just node:crypto we could handoff the react-native polyfill to the developer.

[dplewis]

@dblythy Do you mind if I work on your branch? I see you have a few ES Module issues too.

[dplewis]

@dblythy

• I removed the need for you to polyfill Crypto for React-Native feat: Replace CryptoJS with Web Crypto #2501
• I believe this process could be made easier if we convert the project to an ES6 module first. Vite has default outputs for type:module

[mtrezza]

See #2501 (comment). I would like to break this chain here, as we cannot merge a breaking change into the Parse JS SDK. This PR is already holding back #2402. So if there's an easy workaround to get this PR merged without depending on #2501, then please let's do that.

[dblythy]

@dplewis you are welcome to work off this branch if you would like 😊

Also had a small problem with 2 of the localstorage tests

[parseplatformorg]

🎉 This change has been released in version 6.2.0-alpha.3

[parseplatformorg]

🎉 This change has been released in version 7.0.0