7ebff31475
Version 3 of the kit: - Radix UI replaced with Base UI (using the Shadcn UI patterns) - next-intl replaces react-i18next - enhanceAction deprecated; usage moved to next-safe-action - main layout now wrapped with [locale] path segment - Teams only mode - Layout updates - Zod v4 - Next.js 16.2 - Typescript 6 - All other dependencies updated - Removed deprecated Edge CSRF - Dynamic Github Action runner
62 lines
1.7 KiB
Plaintext
62 lines
1.7 KiB
Plaintext
---
|
|
status: "published"
|
|
title: 'Troubleshooting module not found issues in the Next.js Supabase kit'
|
|
label: 'Modules not found'
|
|
order: 6
|
|
description: 'Troubleshoot issues related to modules not found in the Next.js Supabase SaaS kit'
|
|
---
|
|
|
|
Let's walk through common "Module not found" errors and how to fix them in your Makerkit project.
|
|
|
|
This issue is mostly related to either dependency installed in the wrong package or issues with the file system.
|
|
|
|
### 1. Windows Paths issues
|
|
|
|
Windows has a limitation for the maximum path length. If you're running into issues with paths, you can try the following:
|
|
|
|
1. Move the project closer to the root of your drive
|
|
2. Use a shorter name for the project's folder name
|
|
3. Please Please Please use WSL2 instead of Windows
|
|
|
|
### 2. Windows OneDrive Conflicts
|
|
|
|
OneDrive can cause file system issues with Node.js projects. If you're using Windows with OneDrive:
|
|
|
|
1. Move your project outside of OneDrive-synced folders
|
|
2. Or disable OneDrive sync for your development folder
|
|
|
|
|
|
### 3. Dependency Installation Issues
|
|
|
|
The most common cause is incorrect dependency installation. Here's how to fix it:
|
|
|
|
```bash
|
|
# First, clean your workspace
|
|
pnpm run clean:workspaces
|
|
pnpm run clean
|
|
|
|
# Reinstall dependencies
|
|
pnpm install
|
|
```
|
|
|
|
If you're adding new dependencies, make sure to install them in the correct package:
|
|
|
|
```bash
|
|
# For main app dependencies
|
|
pnpm install my-package --filter web
|
|
|
|
# For a specific package
|
|
pnpm install my-package --filter @kit/ui
|
|
```
|
|
|
|
For example, if you're using the dependency in the `@kit/ui` package, you should install it in the `@kit/ui` package:
|
|
|
|
```bash
|
|
pnpm add my-package --filter "@kit/ui"
|
|
```
|
|
|
|
If it's in the main app, you should install it in the main app:
|
|
|
|
```bash
|
|
pnpm add my-package --filter web
|
|
``` |