Martin Man

I am +1 for updating the docs. The syntax @chadpav used actually exists in one of the early parse server docs but was likely not supported for many years now....

@mtrezza I would love to test it but currently I am low-priority stuck on two conflicting issues: ``` const ParsePushAdapter = require('@parse/push-adapter').ParsePushAdapter; ``` that I used to work around push...

> @mman does this help you? [parse-community/parse-server#9316 (comment)](https://github.com/parse-community/parse-server/issues/9316#issuecomment-2379043778) I think it's actually this one: https://github.com/parse-community/parse-server/issues/7559 with workaround mentioned here: https://stackoverflow.com/questions/77638089/how-to-make-parse-server-detect-im-using-esm-now where instead of passing a cloud code path to Parse...

@mtrezza @vahidalizad Just wanted to confirm that I have finally updated my alpha staging environment with this PR and have not seen any issues in testing. Good job!

I know this bug is rather old but here is a snippet of the cloud code that I'm using to remove ``_PushStatus`` entries once the push goes though to avoid...

Just for completeness... this is the TTL based index that makes it easier to get rid of `_PushStatus` entries automatically after some time. The key is `"expireAfterSeconds" : 300` ```...

All good and valid questions, I will let Lee chime in and try to answer as best as I can meanwhile. The way `enet_host_service` works is rooted in history of...

@jimnor0xF In your deployment try this to figure out what push adapter version was pulled in. For 6.x chances are that it's the old version without the fixes. ``` €...

Attempt to address this cleanly here: https://github.com/nodejs/readable-stream/pull/542

Addressed by #542