next@>13.2.2 causes "keystone build" to hang

[dfinton]

Steps to reproduce
After I update my keystone dependencies, yarn build hangs indefinitely on:

info  - Creating an optimized production build ...

yarn dev does complete and serves data, and I am able to login to the admin UI. It's only when trying to make a production build does it hang.

I checked for legacy issues matching what I was seeing on the various forums but nothing appears to be applicable to this circumstance. I'm not running out of processes or memory. I tried blowing away the existing build directory but nothing seems to work, and without an error message I don't have a lot to go on in terms of troubleshooting.

What was expected
Either for yarn build to complete without errors, or in the event of a failure, to report an error message

Screenshot

Contextual Information

$ node --version
v18.15.0
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 22.04.2 LTS
Release:        22.04
Codename:       jammy

package.json dependencies before update:

    "@keystone-6/auth": "^5.0.0",
    "@keystone-6/core": "^3.0.1",
    "@keystone-6/fields-document": "^5.0.0",
    "dotenv": "^16.0.3",
    "typescript": "^4.8.0"

after update:

    "@keystone-6/auth": "^7.0.0",
    "@keystone-6/core": "^5.1.0",
    "@keystone-6/fields-document": "^7.0.0",
    "dotenv": "^16.0.3",
    "typescript": "^4.8.0"

[dfinton]

Just wanted to leave an update: I am able to reproduce this issue by creating a brand new app with keystone-create-app. Even with an unmodified app, the build process hangs.

$ yarn create keystone-app surazal-net-cms
yarn create v1.22.19
...
Done in 33.24s.
$ cd surazal-net-cms
$ yarn dev
yarn run v1.22.19
$ keystone dev
...
event - compiled client and server successfully in 4.7s (1699 modules)
✅ Admin UI ready
^C
$ yarn build
yarn run v1.22.19
$ keystone build
...
info  - Creating an optimized production build ...

If I run yarn build --no-ui the process does not hang and completes successfully, but of course yarn start fails because it can't run the UI and aborts with an error.

[dfinton]

Further update: I tried this on my other platform to rule out an issue on my local development environment. The build also hangs on my Debian server:

$ lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description:    Debian GNU/Linux 11 (bullseye)
Release:        11
Codename:       bullseye

I also ran npm cache clean --force and ran everything from scratch to rule out a corrupted cache in both of my environments.

[dcousens]

@dfinton, @borisno2 and I noticed this bug late last week, and it's a result of using next>13.2.2.
In our recent pull request #8398, we fixed next to this version and are preparing a release in the next few days.

1501892#diff-0b810c38f3c138a3d5e44854edefd5eb966617ca84e62f06511f60acc40546c7R283

I don't know exactly what the problem is, but, the resolution is to not use next>13.2.2 for now.

[borisno2]

Tested with the the following version of Next

• 13.2.3 build works
• 13.2.4 build hangs as described
• latest canary build build works

So it is just with Next version 13.2.4 where the build is broken and should be resolved in 13.2.5

[AllanFerencz]

@borisno2 Looks like Next is on 13.3.0 now.

I still have the hanging build issue

[dcousens]

@AllanFerencz can you help with a reproduction?

[AllanFerencz]

Sure, It's reproducible with the current version of Keystone 6.

1. Make a new project
2. yarn
3. yarn build - Hanging happens here

The latest version of Next in the package.json is pointing to version 13.2.2

[borisno2]

Hi @AllanFerencz
I am unable to replicate. I am doing the following

1. yarn create keystone-app
2. cd into directory
3. yarn build
   Build happens as expected, if I use yarn why next I can see that it is installing next@13.3.0.

Are you using yarn create keystone-app to make a new project or another method?

[AllanFerencz]

Awesome, It's working as expected. :)

[borisno2]

Great, I'll close this issue now then. Thanks for letting us know