rburgst

in `package.json` the `publish:release` command is defined as follows ```json "scripts": { "publish:release": "yarn npm publish", } ```

any news on that, running into this problem too

The linked article and repo still have the problem that HMR is not properly enabled, it leaves this ``` NOTICE Hot Module Replacement (HMR) is enabled for the dev server....

I have a similar problem as @mmachatschek when running `pnpm install --shamefully-hoist` it fails since its trying to resolve all lists where one of them does rely on the prisma...

ok, the issue with the constant recompiling seems to be #7902. I can confirm that setting the resolution as described in https://github.com/keystonejs/keystone/issues/7902#issuecomment-1243101439 fixes it for pnpm as well.

Actually I was too fast, now after getting the install fixed, keystone wont run properly, I am now seeing this issue: https://github.com/keystonejs/keystone/issues/6848

What do I need to do to get this change reviewed?

anyone home?

I have rebased it on to main, @dcousens any chance to get this reviewed?

@gautamsi that would obviously be even better. Then however, I guess keystone would need to have a built-in version field which would then utilize this new feature. With my patch...