Element type is invalid when building Next.js 14 project

[JollyMicheal]

Link to the code that reproduces this issue

https://github.com/JollyMicheal/rhine

To Reproduce

1. Set up a Next.js 14 project with the provided project structure and dependencies.
2. Create the page.js, layout.js, and heroSection.js components as shown in the code examples.
3. Run npm run dev to start the development server (works fine).
4. Run npm run build to create a production build.
5. Observe the "Error: Element type is invalid" error during the build process.

Current vs. Expected behavior

• Current behavior: When running npm run build, the project throws an "Error: Element type is invalid" error during the prerendering of the "/" page. The error suggests that an invalid element type is encountered, expecting a string or a class/function but getting an object.
• Expected behavior: The project should build successfully without any errors, and the production build should be generated correctly.

Provide environment information

{
  "name": "rhine",
  "version": "0.1.0",
  "private": true,
  "scripts": {
    "dev": "tinacms dev -c \"next dev\"",
    "build": "tinacms build && next build",
    "start": "tinacms build && next start",
    "tinainit": "tinacms init backend",
    "lint": "next lint"
  },
  "dependencies": {
    "@emotion/cache": "^11.11.0",
    "@emotion/react": "^11.11.4",
    "@emotion/styled": "^11.11.5",
    "@mui/icons-material": "^5.15.15",
    "@mui/material": "^5.15.15",
    "next": "14.2.1",
    "react": "^18",
    "react-dom": "^18",
    "tinacms": "^1.6.1"
  },
  "devDependencies": {
    "@tinacms/cli": "^1.5.43",
    "eslint": "^8",
    "eslint-config-next": "14.2.1"
  }
}
Operating System: macOS
Browser: Not applicable (Node.js environment)

Which area(s) are affected? (Select all that apply)

Not sure

Which stage(s) are affected? (Select all that apply)

next build (local), Other (Deployed)

Additional context

• I've tried various troubleshooting steps, such as:
  • Ensuring the 'use client' directive is placed at the top of the relevant component files
  • Checking that all components are properly defined and exported
  • Verifying the correct import paths for components and dependencies
  • Commenting out individual components to isolate the issue
• The issue seems to be related to either the PageLayout component or the HomeHeroSection component.
• Commenting out both the PageLayout and HomeHeroSection components in the page.js file allows the build to succeed.
• I suspect there might be an incompatibility or missing configuration related to the Material-UI components or styling system.
• I've provided a minimal reproducible example of the relevant code in the issue description.

File structure

Sure! Here's the file structure based on the information provided in the image:

rhine/
├── public/
│   └── favicon.ico
└── src/
    ├── app/
    │   ├── globals.css
    │   ├── layout.js
    │   ├── page.js
    │   └── page.module.css
    ├── components/
    │   ├── common/
    │   │   ├── appbar/
    │   │   │   └── index.js
    │   │   └── layout/
    │   │       ├── index.js
    │   │       └── pageLayout.module.css
    │   └── heroSection/
    │       ├── homeHeroSection.module.css
    │       └── index.js
    ├── pages/
    ├── tina/
    │   └── __generated__/
    │       └── client.js
    ├── utils/
    ├── .env
    ├── .eslintrc.json
    ├── .gitignore
    ├── jsconfig.json
    ├── next.config.mjs
    ├── package.json
    └── README.md

The project structure includes the following main directories and files:

• public/: Contains public assets such as favicon.ico.
• src/: Contains the main source code of the Next.js application.
  • app/: Contains the Next.js app directory files.
    • globals.css: Global CSS styles.
    • layout.js: Layout component for the app.
    • page.js: The main page component.
    • page.module.css: CSS module for the main page component.
  • components/: Contains reusable components used in the application.
    • common/: Contains common components.
      • appbar/: Contains the index.js file for the app bar component.
      • layout/: Contains the index.js file for the layout component and the corresponding CSS module.
    • heroSection/: Contains the index.js file for the hero section component and the corresponding CSS module.
  • pages/: Contains additional pages (if any) in the Next.js pages directory structure.
  • tina/: Contains files related to Tina CMS.
    • __generated__/: Contains the generated client.js file.
  • utils/: Contains utility functions or helper modules.
• .env: Environment variables file.
• .eslintrc.json: ESLint configuration file.
• .gitignore: Git ignore file.
• jsconfig.json: JavaScript configuration file.
• next.config.mjs: Next.js configuration file.
• package.json: npm package configuration file.
• README.md: Project readme file.

Please note that this is a simplified representation of the file structure based on the provided image. The actual project may contain additional files or directories that are not shown in the image.

Please let me know if you need any further information or clarification. I appreciate any help or guidance in resolving this issue. Thank you!

[github-actions]

We could not detect a valid reproduction link. Make sure to follow the bug report template carefully.

Why was this issue closed?

To be able to investigate, we need access to a reproduction to identify what triggered the issue. We need a link to a public GitHub repository (template for App Router, template for Pages Router), but you can also use these templates: CodeSandbox: App Router or CodeSandbox: Pages Router.

The bug template that you filled out has a section called "Link to the code that reproduces this issue", which is where you should provide the link to the reproduction.

• If you did not provide a link or the link you provided is not valid, we will close the issue.
• If you provide a link to a private repository, we will close the issue.
• If you provide a link to a repository but not in the correct section, we will close the issue.

What should I do?

Depending on the reason the issue was closed, you can do the following:

• If you did not provide a link, please open a new issue with a link to a reproduction.
• If you provided a link to a private repository, please open a new issue with a link to a public repository.
• If you provided a link to a repository but not in the correct section, please open a new issue with a link to a reproduction in the correct section.

In general, assume that we should not go through a lengthy onboarding process at your company code only to be able to verify an issue.

My repository is private and cannot make it public

In most cases, a private repo will not be a sufficient minimal reproduction, as this codebase might contain a lot of unrelated parts that would make our investigation take longer. Please do not make it public. Instead, create a new repository using the templates above, adding the relevant code to reproduce the issue. Common things to look out for:

• Remove any code that is not related to the issue. (pages, API routes, components, etc.)
• Remove any dependencies that are not related to the issue.
• Remove any third-party service that would require us to sign up for an account to reproduce the issue.
• Remove any environment variables that are not related to the issue.
• Remove private packages that we do not have access to.
• If the issue is not related to a monorepo specifically, try to reproduce the issue without a complex monorepo setup

I did not open this issue, but it is relevant to me, what can I do to help?

Anyone experiencing the same issue is welcome to provide a minimal reproduction following the above steps by opening a new issue.

I think my reproduction is good enough, why aren't you looking into it quickly?

We look into every Next.js issue and constantly monitor open issues for new comments.

However, sometimes we might miss one or two due to the popularity/high traffic of the repository. We apologize, and kindly ask you to refrain from tagging core maintainers, as that will usually not result in increased priority.

Upvoting issues to show your interest will help us prioritize and address them as quickly as possible. That said, every issue is important to us, and if an issue gets closed by accident, we encourage you to open a new one linking to the old issue and we will look into it.

Useful Resources

• How to Contribute to Open Source (Next.js)
• How to create a Minimal, Complete, and Verifiable example
• Reporting a Next.js bug
• Next.js Triaging issues