Daniel Cousens

@MartinDawson I think the conclusion is that we want to change this pull request to support the image types to be configurable by users, instead of prescribed by `@keystone-6/*`. We...

See feature request https://github.com/keystonejs/keystone/discussions/8913

I cannot reproduce. My steps ```bash mkdir issue-7066 cd issue-7066/ pnpm init pnpm install @keystone-6/core vim keystone.ts ``` ```typescript import { config } from '@keystone-6/core' export default config({ db: {...

I think we can add this functionality with the caveat that no `read` hooks could exist for the underlying item or fields... Alternatively, we can change the type of `item`...

@MurzNN if you still need this, could you open a feature request GitHub discussion?

Cannot reproduce, `keystone.js` works as intended now.

Reproduced this problem, `keystone build` and `keystone dev`, using a plain `keystone.js` entry, still results in `yarn` adding `typescript` to your `devDependencies`. ``` $ keystone build ✨ Building Keystone ✨...

I don't think we want to encourage `process.env.PORT` from our `keystone *` scripts, as you should be configuring this yourself in your own Keystone configuration - but for now it...

Cannot reproduce in newest `@keystone-6/core`, please comment or open a new issue if you can

@scoussens depending on how you unpack these into your `lists` object, the order of definition will define the order of the definitions in `schema.prisma` and `schema.graphql`. Potentially, we should ensure...