Tonni Akter - Full Stack Web Developer

⚡ Next.js Cache Issue? Why Your Updates Are Not Showing

Sometimes, after deploying a Next.js website, your users see old content.

The culprit: caching issues in ISR (Incremental Static Regeneration) or browser cache.

Quick fix:

export async function getStaticProps() {
return {
props: { data },
revalidate: 10, // regenerates every 10 seconds
}
}

💡 Always set proper revalidation time and clear CDN cache for instant updates.

Question for developers: How do you manage ISR caching on large projects?

🚀 **Full Stack React & Node.js E-Commerce Project**

Excited to share one of my **Full Stack Web Development Projects** that I built using **React.js and Node.js**.

🔗 Live Demo: https://shopcart.reactbd.com/

This project is a **modern eCommerce website** designed to demonstrate how scalable and fast web applications can be built using the **MERN stack architecture**.

💻 **Technology Used**
✔ React.js (Frontend UI Development)
✔ Node.js (Backend Server)
✔ REST API Integration
✔ Modern Component Based Architecture
✔ Responsive UI Design

🛒 **Core Features**
• Product Listing System
• Shopping Cart Functionality
• Dynamic UI Rendering
• Fast React Performance
• Clean & Scalable Code Structure

As a **Full Stack Developer**, I focus on building **fast, scalable and SEO-friendly web applications** for businesses and startups.

If you need a **React, Next.js, Node.js or MERN Stack website**, feel free to connect with me.

👩‍💻 **Tonni Akter**
Full Stack Developer (React | Node | MERN)

; ; ; ; ; ; ; ; ; ; ; ; ; ; ;

⚡ Why Your Next.js Website Loads Slowly on First Visit

Even well-built Next.js websites can feel slow on the first visit.

This usually happens because:

• Large JavaScript bundle
• Too many API requests
• Heavy images

💡 Optimizing first contentful paint (FCP) is critical for user experience.

Improvement methods:

• Image optimization
• Lazy loading components
• Reducing bundle size

🚀 Next.js Website Works Locally But Fails After Deployment

Many developers face this issue.

The website runs perfectly in development.

But after deployment:

❌ Page crashes
❌ Environment variables missing
❌ API routes failing

The reason usually involves:

• Incorrect environment configuration
• Missing dependencies
• Build errors

💡 Always test production build locally.

npm run build
npm start

💡 Why Some Third-Party Scripts Break Next.js Pages

While integrating a chat widget in a Next.js website, the page suddenly crashed.

The reason?

The script tried to access:

window
document

But during Server Side Rendering, these objects do not exist.

Fix

Load scripts only in the browser:

useEffect(()=>{
loadScript()
},[])

💡 This prevents server-side crashes.

Question 👇

Have you ever faced SSR errors caused by third-party scripts?

⚡ Next.js Edge Runtime Not Supporting Some Node.js APIs

When trying to deploy a middleware function using Edge Runtime, I faced a limitation.

Some Node.js modules simply did not work.

Example:

fs module
crypto module

These modules are not supported in Edge Runtime environment.

💡 Developers must use Web APIs instead of Node APIs when writing Edge functions.

Question for developers 👇

Have you tried using Edge Runtime for performance improvements?

⚠️ Next.js Build Size Too Large? Your Website Might Be Slower Than You Think

While analyzing a production build in Next.js, I noticed something concerning.

The build output showed:

📦 Large JavaScript bundle

This usually happens when developers import heavy libraries unnecessarily.

Example problem:

import * as lodash from "lodash"

Instead use:

import debounce from "lodash/debounce"

💡 Smaller bundle size means:

• Faster website load
• Better SEO score
• Improved mobile performance

Question 👇

Do you check bundle size before deploying a project?

🔎 Why Your Next.js Website Is Not Showing Correct SEO Meta Tags

While testing a Next.js project, I noticed something strange.

The page title and description looked correct in the code.

But when sharing the link on Facebook or LinkedIn, the preview showed:

❌ Wrong title
❌ Missing description
❌ Incorrect image

The reason?

The meta tags were not rendered properly on the server side.

Example fix using Next.js Head:

import Head from "next/head"


My Website



💡 Proper meta tags improve:

• Google search ranking
• Social media preview
• Website click-through rate

Question for developers 👇

Do you manually manage SEO tags or use an SEO library?



Tonni Akter

📄 Next.js Page Not Updating Even After Changing Data?

This issue surprised me when working with Static Site Generation (SSG) in Next.js.

I updated the database.

But the website still showed old content.

The reason?

The page was generated during build time only.

Example:

export async function getStaticProps(){
return {props:{data}}
}

This means the page does not update until the site is rebuilt.

Fix

Use Incremental Static Regeneration (ISR):

revalidate:60

Now the page refreshes every 60 seconds automatically.

💡 This is one of the biggest differences between:

• Static Generation
• Server Side Rendering

Understanding this helps developers choose the right rendering strategy.

Question 👇

Do you prefer SSR or SSG when building production apps?

⚡ Next.js API Routes Becoming Slow?

While building backend APIs inside a Next.js project, I noticed something unusual.

The frontend UI was optimized.

But API responses were taking 3–5 seconds.

After analyzing the code, the issue was inside the API route.

Example:

const data = await db.users.find()

The database query was returning too much data, which slowed down the response.

Fix

Optimize database queries:

const data = await db.users.find().limit(10)

💡 Efficient APIs improve:

• Website performance
• User experience
• SEO ranking

Because slow APIs mean slow websites.

Question for developers 👇

Which database do you use most with Next.js?

🔐 User Logged In… But Logged Out After Refresh?

This is a very common issue when building authentication systems in Next.js applications.

Everything seems to work:

✔ Login successful
✔ Dashboard loads

But when the user refreshes the page…

❌ Session disappears

The user becomes logged out again.

After debugging the authentication system, the problem is usually related to cookie configuration.

Common mistakes include:

• Token stored only in React state
• Missing cookie expiration
• Secure cookie settings not configured

Example solution:

Store the session token in a cookie:

res.setHeader("Set-Cookie","token=abc123; HttpOnly; Path=/")

💡 Proper session storage ensures users stay logged in across page refresh and navigation.

Question for developers 👇

Do you prefer JWT authentication or session-based login?

🚨 Next.js Middleware Redirect Loop — A Bug That Can Crash Your Website

While implementing authentication in a Next.js project, I once faced a strange problem.

The login system worked perfectly.

But after deploying the website, users started reporting:

⚠️ “Too many redirects” error

The page kept refreshing again and again.

After debugging the middleware, I discovered the issue.

The middleware was redirecting every route to /login, including the login page itself.

Example problem:

if(!user){
return NextResponse.redirect("/login")
}

Since /login also triggered the middleware, it created an infinite redirect loop.

Fix

Exclude authentication routes:

if(!user && pathname !== "/login"){
return NextResponse.redirect("/login")
}

💡 Middleware is powerful in Next.js, but one small logic mistake can break the entire website.

Question for developers 👇

Have you ever created an infinite redirect loop by mistake?