2023-04-18
2768
#nextjs
Oghenetega Denedo
144428
Apr 18, 2023 â‹… 9 min read

Learn how to build a monorepo in Next.js

Oghenetega Denedo I'm a curiosity-driven software engineer with a focus on building reliable software that's easy to maintain and follows industry best practices.

Recent posts:

6 Hidden Gems In The JavaScript API You Should Be Using

6 hidden gems in the JavaScript API you should be using

Explore underrated JavaScript APIs like `structuredClone` and `AbortController` that let you build dynamic, performant, and user-friendly apps.

Rahul Padalkar
Apr 28, 2025 â‹… 10 min read
next js environmental variables

How to configure Next.js environmental variables

Learn how to manage environment variables in Next.js, which influence how an application behaves in different contexts and environments.

Joseph Mawa
Apr 25, 2025 â‹… 9 min read
useActionState in React

useActionState in React: A practical guide with examples

Discover how React’s useActionState Hook makes it easier to handle user actions, especially form submissions and async state changes.

Rishi Purwar
Apr 25, 2025 â‹… 5 min read
three js vs babylon js

Three.js vs. Babylon.js: Which is better for 3D web development?

Compare two libraries that support creating 3D experiences in the browser. Learn how to get started with each, their core features, and key differences.

Elijah Asaolu
Apr 24, 2025 â‹… 7 min read
View all posts

8 Replies to "Learn how to build a monorepo in Next.js"

  1. hi! excellent tutorial !
    I have a little bug at the end of tut, after config next.config.js file and restart.
    ->Module not found: Can’t resolve ‘ui’ -> import { Button } from “ui”
    (the root node_modules is ok, ‘ui’ is present)

    1. Thanks for your comment! We’ve updated the article with an additional code snippet from the author to address this.

  2. I’m facing a problem with the ESLint configuration. I followed the tutorial to the letter, but it seems ESLint now uses a flat config format, and stipulates a single `eslint.config.js` file in the root directory. Couldn’t find a workaround.

Leave a Reply