fix: Incorrect Parse import uses browser build instead of Node build#511
Conversation
|
🚀 Thanks for opening this pull request! |
✅ Snyk checks have passed. No issues have been found so far.
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
|
Caution Review failedThe pull request is closed. 📝 WalkthroughWalkthroughParse module import paths are updated from 'parse' to 'parse/node' across five files in the push notification adapter codebase. No functional changes or interface modifications are present. Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~5 minutes Suggested reviewers
✨ Finishing Touches
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
## [8.3.1](8.3.0...8.3.1) (2026-02-21) ### Bug Fixes * Incorrect `Parse` import uses browser build instead of Node build ([#511](#511)) ([66cc9f4](66cc9f4))
|
🎉 This change has been released in version 8.3.1 |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #511 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 8 8
Lines 1172 1172
=========================================
Hits 1172 1172 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
Pull Request
Issue
Incorrect
Parseimport uses browser build instead of Node buildSummary by CodeRabbit