Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot read properties of undefined (reading 'nextConfig') #107

Open
midnightcodr opened this issue May 26, 2023 · 5 comments
Open

Cannot read properties of undefined (reading 'nextConfig') #107

midnightcodr opened this issue May 26, 2023 · 5 comments

Comments

@midnightcodr
Copy link

Describe the bug
Trying out nest-next with the most current versions

    "@nestjs/common": "^9.0.0",
    "@nestjs/core": "^9.0.0",
    "@nestjs/platform-express": "^9.0.0",
    "nest-next": "^10.1.0",
    "next": "^13.4.4",

With [email protected] I am getting the following error and server is not able to start. Downgrading to a lower version such as 13.3.1 the problem went away.

  • event compiled client and server successfully in 668 ms (158 modules)
  • wait compiling...
    [Nest] 98752 - 05/25/2023, 11:11:50 PM ERROR [ExceptionHandler] Cannot read properties of undefined (reading 'nextConfig')
    TypeError: Cannot read properties of undefined (reading 'nextConfig')
    at Function. (/path/to/project/node_modules/nest-next/dist/render.module.js:37:30)
    at Generator.next ()
    at fulfilled (/path/to/project/node_modules/nest-next/dist/render.module.js:14:58)

Expected behavior
Start nest server successfully

Version

  • next.js:13.4.4
  • nest:9.0.0
  • nest-next: 10.1.0
@layunne
Copy link

layunne commented Jun 12, 2023

i am having the same error. This was after [email protected]

@raychunghk
Copy link

To be more explicit, in the RenderModule, in [email protected], it successfully passes NextServer to forRootAsync, but not after this version.

NextServer { options: { dev: true } }

@raychunghk
Copy link

I filed the issue to the next js repo issues
vercel/next.js#51466

@kaminion
Copy link

kaminion commented May 17, 2024

I filed the issue to the next js repo issues
vercel/next.js#51466

So, It's going on.. it's not solved I saw that.

@Amantel
Copy link

Amantel commented Jul 29, 2024

Seems like a deal breaker to me

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants