Next.js

React • 2025-06-02

Custom 404 Pages with Internationalized Routing in Next.js

Learn how to handle 404 pages in an internationalization scenario using Next.js's App Router, including conventional routing rules, capturing unmatched routes, and creating a multilingual 404 component.

Next.js • 2025-04-02

"Type 'bigint' is not assignable to ReactNode" Error in Next.js 14.2.2

Resolve the 'Type 'bigint' is not assignable to ReactNode' error in Next.js 14.2.2 through version consistency and reinstalling dependencies.

Next.js • 2025-03-28

Solution to the Asynchronous Parameter Type Error in Next.js 15 Routing

In the development of Next.js 15 applications, when attempting to use asynchronous parameters, type mismatch errors may occur because Next.js has specific expectations for the type structure of the params object.

Next.js • 2025-03-28

Solution to the Problem of NextJS Middleware Not Triggering

When developing with NextJS, middleware is an important feature. However, different versions of NextJS have different requirements for the location and configuration of middleware files, which may cause the middleware not to be triggered as expected.

Next.js • 2025-03-27

Mastering Error Handling for Server Actions in Next.js

Learn best practices for handling errors in Next.js server actions and presenting them effectively to users, including useFormState and useActionState.

Next.js • 2025-03-27

Clean Error Handling for Server Components in NextJS Production Mode with Obfuscated Error Messages

In a NextJS 14.0.3 application integrated with TypeScript and an App router, along with a separate Django Rest Framework backend API, ensuring consistent error handling for both client-side and server-side errors is crucial. However, there are several challenges that developers often encounter, especially when dealing with production-mode obfuscated error messages.

React • 2025-03-27

Resolving the Issue of Inability to Deploy NextJS Project with next-intl to Github Pages

In a NextJS project, the next-intl library was used to implement internationalization features. The project was built and ran normally in the development environment, but problems occurred when attempting to deploy it to Github Pages.