cdk-nextjs: Build error with .next/standalone on Next 13.1.1

Describe Behavior

When building the next project with cdk-nextjs-standalone, it does not output a .next/standalone folder, despite the output set to standalone in next.config.js

Additional Information

The standalone folder does appear when running next build from the root of the next project, however

Versions used:

Dependencies

next: 13.1.1 cdk-nextjs-standalone: ^2.0.4 aws-cdk-lib: ^2.50.0 constructs: ^10.0.5

devDependencies

aws-cdk: ^2.50.0 esbuild: ^0.15.18

About this issue

  • Original URL
  • State: closed
  • Created a year ago
  • Reactions: 1
  • Comments: 26 (12 by maintainers)

Most upvoted comments

That’s something related on your machine. Not sure why your connection is getting refused. I deployed using the steps I posted above and didn’t get that error.

Thank you for the insights. The monorepo that contains the project was forcing an earlier version of aws-cdk-lib, constructs, and esbuild.

The standalone folder appears now. This issue is resolved.

Do you by chance happen to have an example usage of cdk-nextjs?