### 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? --> crypto-js and react-native-crypto-js are deprecated. crypto-js is an optional dependency because of the issues. ### Feature / Enhancement Description <!-- What is the concept of the functionality and how should it be implemented? --> These should replaced with node:crypto and [react-native-quick-crypto](https://github.com/margelo/react-native-quick-crypto) respectfully. `quick-crypto` is a well maintained drop in replacement for `node:crypto`. `node:crypto` is easily polyfilled for browsers ### Example Use Case <!-- What is an example use case in steps (1. / 2. / 3. / etc.) that describes the functionality? --> This will also help with finishing rollup / vite support https://github.com/parse-community/Parse-SDK-JS/pull/2425 ### Alternatives / Workarounds <!-- Which alternatives or workarounds exist currently? --> Build our own isomorphic CryptoController without dependencies or document how a user could create there own CryptoController
Activity
parse-github-assistant commentedon Mar 12, 2025
🚀 Thanks for opening this issue! We are excited about your ideas for improvement!