Skip to content

fix: Incorrect Parse import uses browser build instead of Node build#511

Merged
mtrezza merged 1 commit intoparse-community:masterfrom
mtrezza:fix/parse-imports
Feb 21, 2026
Merged

fix: Incorrect Parse import uses browser build instead of Node build#511
mtrezza merged 1 commit intoparse-community:masterfrom
mtrezza:fix/parse-imports

Conversation

@mtrezza
Copy link
Member

@mtrezza mtrezza commented Feb 21, 2026

Pull Request

Issue

Incorrect Parse import uses browser build instead of Node build

Summary by CodeRabbit

  • Chores
    • Updated internal module imports across push notification adapters to improve dependency resolution.

@parse-github-assistant
Copy link

🚀 Thanks for opening this pull request!

@parseplatformorg
Copy link
Contributor

Snyk checks have passed. No issues have been found so far.

Status Scanner Critical High Medium Low Total (0)
Open Source Security 0 0 0 0 0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

@coderabbitai
Copy link

coderabbitai bot commented Feb 21, 2026

Caution

Review failed

The pull request is closed.

📝 Walkthrough

Walkthrough

Parse 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

Cohort / File(s) Summary
Parse Import Update
src/APNS.js, src/EXPO.js, src/FCM.js, src/ParsePushAdapter.js, src/WEB.js
Import path for Parse module changed from 'parse' to 'parse/node' in each file. No functional or interface changes.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~5 minutes

Suggested reviewers

  • dplewis
✨ Finishing Touches
  • 📝 Generate docstrings (stacked PR)
  • 📝 Generate docstrings (commit on current branch)
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@mtrezza mtrezza merged commit 66cc9f4 into parse-community:master Feb 21, 2026
6 of 7 checks passed
@mtrezza mtrezza deleted the fix/parse-imports branch February 21, 2026 01:01
parseplatformorg pushed a commit that referenced this pull request Feb 21, 2026
## [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))
@parseplatformorg
Copy link
Contributor

🎉 This change has been released in version 8.3.1

@codecov
Copy link

codecov bot commented Feb 21, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.00%. Comparing base (02e6b6a) to head (f7d64a3).
⚠️ Report is 3 commits behind head on master.

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.
📢 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants