Unable to start Parse Server 7.4.0 with Node > 22: Push Adapter fails with "Adapter prototype don't match expected prototype"

[pocketcolin]

New Issue Checklist

• Report security issues confidentially.
• Any contribution is under this license.
• Before posting search existing issues.

Issue Description

After upgrading my server to Parse Server 7.4.0, I discovered that I no longer can start the server with when running a Node version > 22. You can actually fix this issue by fully disabling the push worker and adding the following to your Parse config:

push: {
    queueOptions: {
        disablePushWorker: true
    }
},

Steps to reproduce

1. Run Parse Server 7.4.0 (I use it with Express but I'm guessing that's not relevant here) with Node v22.x.

Actual Outcome

In my console, I get the following error:

Error: Adapter prototype don't match expected prototype
    at AdaptableController.validateAdapter (/Users/pocketcolin/server/node_modules/parse-server/lib/Controllers/AdaptableController.js:66:13)
    at new PushWorker (/Users/pocketcolin/server/node_modules/parse-server/lib/Push/PushWorker.js:32:34)
    at Object.getPushController (/Users/pocketcolin/server/node_modules/parse-server/lib/Controllers/index.js:210:18)
    at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
    at async ParseServer.start (/Users/pocketcolin/server/node_modules/parse-server/lib/ParseServer.js:174:30)
    at async start (/Users/pocketcolin/server/dist/index.js:239:5)
    at async throng (/Users/pocketcolin/server/node_modules/throng/lib/throng.js:24:12)

Expected Outcome

Parse Server starts up normally.

Environment

"node": "22.11.0",
"express": "4.21.0",
"parse-server": "7.4.0"

Server

• Parse Server version: 7.4.0

[parse-github-assistant]

Thanks for opening this issue!

• 🚀 You can help us to fix this issue faster by opening a pull request with a failing test. See our Contribution Guide for how to make a pull request, or read our New Contributor's Guide if this is your first time contributing.

[3011felix]

I also noticed this error on versions < 7.4.0.
I think it's happening since nodejs > 22.11.0

[vctechplus]

Have the same issue, but no crash with node 20.x

[mtrezza]

Thanks for reporting, we're actively looking into this issue.

[pocketcolin]

@3011felix yep agreed on it happening with node > 22.11. I think VS Code debug mode was running a different version of node unbeknownst to me. The PR @dblythy made (#9524) fixes this issue for me.

[parseplatformorg]

🎉 This change has been released in version 8.0.0-alpha.2

[mtrezza]

Reopen for #9525

[dblythy]

@mtrezza what do we need to do to close this?