SaaSHub helps you find the best software and product alternatives Learn more →
Community Alternatives
Similar projects and alternatives to community
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
-
astro-trpc-example
Shows how to mount a tRPC router into an Astro app using `@trpc/server/adapters/fetch`
community reviews and mentions
-
All my NextJs API suddenly returns 504 timeout
![image](https://github.com/vercel/community/assets/15647967/e660fe42-9fbb-449a-a388-d25e68804827)
-
We Need to Talk About Vercel
What a disappointing take.
In fact Lee was looped in six weeks ago; there was an issue with Remix and CDN cache behavior which popped up on GitHub. I mentioned my issues in that thread thinking they were likely related. Lee responded and let me know he would talk to the internal team.[0] However, Lee did nothing that was ever visible to me. Moreover, I completely disagree with your assessment: it should not require Lee or a social media to tackle issues like this, that’s completely unscalable and not a realistic way to run a business.
It’s pretty irresponsible of you to be suggesting folks reach out directly to Lee when frontline support fails. That sucks for Lee and it’s bad for the Vercel business.
To be blunt with you, your comment does not read well. It looks like you’re ignoring very real problems and doing everything you can to dismiss them as “bad faith” when in fact there’s a demonstrable problem which shouldn’t be excused as growing pains but instead addressed head on. This kind of fanboyism doesn’t help anyone and I hope Vercel takes the time to reflect on this feedback and make real, meaningful changes.
[0]: https://github.com/vercel/community/discussions/1559#discuss...
-
How to Build Scalable Architecture for your Next.js Project
The reason we are using v14 instead of v16 for Node is that later in the tutorial we will be deploying on Vercel which unfortunately still does not support Node 16. Perhaps by the time you read this tutorial it might. You can follow the progress here.
- How can one use the components at vercel.com/design?
-
Vercel preview mode not working on prod, but works locally
Having trouble finding help for this one in the next discord / vercel discussion. any help is super appreciated! https://github.com/vercel/community/discussions/336
- Reactjs website not indexable if deployed on Vercel
-
Migrating from Netlify to Cloudflare Workers Sites for 2x Performance
Honestly not that many practical ones. It does improve the behaviour on ipv6 devices, but not significantly. I admit that for me it's more of a "we know it's happening, so I'd like to support companies not dragging their feet" position. It will hopefully come at some point: https://github.com/vercel/community/discussions/47
-
A note from our sponsor - SaaSHub
www.saashub.com | 6 May 2024
Stats
Sponsored