Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Is pusherjs still under active development? #833

Open
KayakinKoder opened this issue Jul 22, 2024 · 11 comments
Open

Is pusherjs still under active development? #833

KayakinKoder opened this issue Jul 22, 2024 · 11 comments

Comments

@KayakinKoder
Copy link

We are paying customers, but looking at your releases, the last was nearly 8 months ago. That doesn't bode well, not even having some small releases for bug fixes/package updates.

Is pusherjs still under active development? If so, why are updates so rare? Thanks.

@isaachinman
Copy link

I raised similar concerns in #702.

If anyone is aware of an alternative client-side package that is compatible with the Pusher protocol and/or Soketi, please let me know.

@hichemfantar
Copy link

@isaachinman Ably is pusher compatible

@isaachinman
Copy link

I'm aware, but it is even more bloated than the Pusher package.

@hichemfantar
Copy link

Is your issue with the bundle size?

@isaachinman
Copy link

Yes, see #702.

I offered actionable and relatively easy steps to substantially improve the package you are distributing to your paying customers.
Is this repository actively maintained?

@hichemfantar
Copy link

hichemfantar commented Oct 11, 2024

I understand but as long as everything is working smoothly then shaving off a few kbs isn't really worth the extra headache. Good server side compression and caching headers should be enough. Maybe throw in lazy loading if first paint is critical.

maybe create a fork with the bundling optimizations you want and use that in your project, then make a pr with your changes?

@isaachinman
Copy link

It's not "shaving a few kbs" – the Pusher package is ~62kb of JavaScript.

I spent about an hour investigating and providing actionable advice to the Pusher team. They thanked me and... closed the issue.

If other users are genuinely interested, I can publish my findings. We can/should continue any further discussion in #702.

This issue has been open for three months with no response from any maintainers, so it's safe to say this repository is not actively maintained.

@KayakinKoder
Copy link
Author

KayakinKoder commented Oct 11, 2024

@isaachinman yes it seems this repo is not actively maintained. Makes me wonder what Pusher's business plans are, given that it seems pusher-js is their primary breadwinner.

On the side note you and @hichemfantar were discussing, Ably looks pretty great. It's 2024, there are far more important things to worry about (such as "is the company actively improving their product"...) than KBs of javascript.

@hichemfantar
Copy link

hichemfantar commented Oct 11, 2024

The 60kB is uncompressed, its 17.7kB with gzip and even less with brotli.
almost every server in existence comes with gzip or brotli.
I agree it could be less but you can always fork and apply the changes you want.

https://bundlephobia.com/package/[email protected]

image

@isaachinman
Copy link

If neither of you are interested in the bundle size discussion, why continue to discuss it in an unrelated issue?

@hichemfantar
Copy link

@isaachinman never said I wasn't interested, I'm discussing solutions until the maintainers push an update.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants