#Error: Could not find the module in the React Client Manifest.

1 messages · Page 1 of 1 (latest)

hard estuary
#

Hi!
I am developing my portfolio website using nextjs 14. I am having a section where to show my projects that I fetch from a DB.
However I am having issues developing the component that shows the projects.

I have my 'projects.tsx' (resumed):

"use server"
async function ProjectsCards() {
    const projects = await getProjects();
    
    return (
        <ProjectList projects={projects}/>        
    )
}

export default async function Projects() {
    return (
        <Suspense fallback={<div>Loading...</div>}>
            <ProjectsCards /> 
        </Suspense>
    );
};


async function getProjects()  {
    const connection = await db();


    try {
        // Perform database operations using the 'connection' object
        // Example: Fetch data from a table
        const [results] = await connection.query("SELECT * FROM projects where lang_code = 'en'");

that is a serber component. Then I have a client component 'project-list.tsx' where I show them.

When loading my main page, it is shown white, and log repeats this error message:

 ⨯ Error: Could not find the module "D:\Desktop\Proyectos\Web Development\elblogdebruno.com - brunomoya.com\Current Design 2023\my-app\src\components\project-list.tsx#" in the React Client Manifest. This is probably a bug in the React Server Components bundler. 
    at stringify (<anonymous>)

What could it be?
thanks
bruno

south duneBOT
#

Hi @hard estuary. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:

#

Based on the information provided in the extracts, it seems like you're encountering a known issue with Next.js where the React Server Components bundler is unable to find a specific module in the React Client Manifest. This issue has been reported by multiple users in different contexts, as seen in the GitHub issues 50243 (https://github.com/vercel/next.js/issues/50243), 54967 (https://github.com/vercel/next.js/issues/54967), 55609 (https://github.com/vercel/next.js/issues/55609), 54253 (https://github.com/vercel/next.js/issues/54253), and 52862 (https://github.com/vercel/next.js/issues/52862).

Unfortunately, the extracts do not provide a specific solution to this issue. However, some users have reported success with various workarounds, such as deleting the .next folder, node_modules folder, and package-lock.json, running npm cache clean --force, and then running npm install. Another user suggested converting all components to server components.

It's also worth noting that this issue seems to have been encountered by users on specific versions of Next.js (e.g., 13.4.10, 13.5.1). If possible, you might want to consider downgrading to a version that didn't have this issue, or upgrading to the latest version or canary release to see if the issue has been resolved.

If none of these suggestions work, I would recommend raising a new issue on the Next.js GitHub repository (https://github.com/vercel/next.js/issues) with detailed information about your setup and how to reproduce the issue.

Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: