Share this page!

Enter URL or ID to Unroll

You can paste full URL like: https://x.com/threadreaderapp/status/1644127596119195649
or just the ID like: 1644127596119195649

How to get URL link on X (Twitter) App

  1. On the Twitter thread, click on or icon on the bottom
  2. Click again on or Share Via icon
  3. Click on Copy Link to Tweet
  4. Paste it above and click "Unroll Thread"!
  5. More info at Twitter Help
Atharva Profile picture
@AtharvaXDevs
Aug 15 • 14 tweets • 6 min read • Read on X
Scrolly
TIRED OF HUNTING NEXTJS OPEN SOURCE PROJECTS ??

-here's a list of some oss projects to whom you can contribute to, which is in nextjs.
THREAD 🧵
1. dub.co

>Dub is the modern link attribution platform for short links, conversion tracking, and affiliate programs.

REPO: github.com/dubincImage
2. Cal @calcom

>The open source Calendly successor. You are in charge of your own data, workflow, and appearance.

REPO: github.com/calcom/cal.comImage
3. MailZero @mail0dotcom

>Zero is an AI-native email client that manages your inbox, so you don't have to.

REPO: github.com/Mail-0/ZeroImage
4. lin.ky

>Linky is the open source link-in-bio that integrates with your favorite platforms to keep your page fresh.

REPO: github.com/trylinky/linkyImage
5. Supabase @supabase

>Supabase is the Postgres development platform.

REPO: github.com/supabase/supab…Image
6. Cap

>Cap is an open-source alternative to Loom, offering lightweight and powerful screen recording capabilities with instant sharing features.

REPO: github.com/CapSoftware/CapImage
7. Medusa

>The most popular open-source platform for commerce.

REPO: github.com/medusajs/medusaImage
8. Fireflies

>The open‑source alternative to Dropbox.

REPO: github.com/faisalsayed10/…Image
9. Payload

>Backend service app.

REPO: github.com/payloadcms/pay…Image
Last and my all time fav
10. Scira @sciraai by @zaidmukaddam

>A minimalist open-source AI search engine better than Perplexity.

REPO: github.com/zaidmukaddam/s…Image
thanks for tuning till here
follow me @AtharvaXDevs for more such informative threads.
I will also try to contribute in one of em', so should you!!
like share repost :)
@threadreaderapp unroll this for oomfies.

• • •

Missing some Tweet in this thread? You can try to force a refresh
　

Keep Current with Atharva

Atharva Profile picture

Stay in touch and get notified when new unrolls are available from this author!

Read all threads

This Thread may be Removed Anytime!

PDF

Twitter may remove this content at anytime! Save it as PDF for later use!

Try unrolling a thread yourself!

how to unroll video
  1. Follow @ThreadReaderApp to mention us!

  2. From a Twitter thread mention us with a keyword "unroll"
@threadreaderapp unroll

Practice here first or read more on our help page!

More from @AtharvaXDevs

Atharva Profile picture
Aug 2
last night, I was skimming TanStack Query docs and went down a rabbit hole on its server-side usage with Next.js. What I found is a total gamechanger for performance. @tan_stack 🤯

>it's a pattern that combines server-side prefetching with client-side hydration to practically eliminate initial page load spinners. When you pair it with Server Actions for mutations, your app feels insanely fast.

here's how it works, a Thread 🧵Image
(1/n) Comparison:

>the old way (Client-Side Fetching):
You go to a restaurant and sit down. Only then do you call the waiter, place your order, and wait for the kitchen to cook and bring you your food. That "waiting for your food" part is the loading spinner your user sees.

>the new way (This Pattern):
You pre-order your meal online. When you arrive at the restaurant, the food is already on your table, hot and ready to eat. No waiting! This is what we're giving our user an instant experience.

will elaborate below.
(2/n) why old way is slow and bad? let's see

>in the traditional client-side fetching model, the data fetching process creates a noticeable delay for the user.

>when a user requests a page, the server initially sends a minimal HTML structure and the required JavaScript. The browser renders this data-less page, forcing the user to see a loading state.

>only after this initial page is loaded does the client-side code execute.
A useEffect hook then triggers a second network request to an API endpoint to fetch the necessary data. The server processes this request and sends the data back. Once the browser receives the data, the component updates its state, triggering a re-render to finally display the content. This multi-step process, where data fetching starts only after the page is already on the client, is the direct cause of the perceived delay and loading indicators.
Read 12 tweets

Did Thread Reader help you today?

Support us! We are indie developers!

This site is made by just two indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3/month or $30/year) and get exclusive features!

Become Premium

Don't want to be a Premium member but still want to support us?

Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal

Or Donate anonymously using crypto!

Ethereum

0xfe58350B80634f60Fa6Dc149a72b4DFbc17D341E copy

Bitcoin

3ATGMxNzCUFzxpMCHL5sWSt4DVtS8UqXpi copy

Thank you for your support!

Follow Us!

Send Email!

:(