Keystone app breaks with interal slice call on getGqlNames

[PhilBookst]

Create a new keystone project via yarn create keystone-app, start the app and access localhost:3000, and the error below is thrown

The app should work

node v v18.18.2, but also tried 20 and 16. tested on all browsers. m1 mac 14.2.1 (if it matters)

[jaycho46]

Is there any way to start project?

[tauantcamargo]

@dcousens do you have any status for it?

[jonesjaycob]

Same here. I'm getting errors on a fresh install.

[jaycho46]

When I put the 'pnpm-lock.yaml' from this repository, the project works fine.

[dcousens]

I can reproduce this problem with yarn, but not pnpm, I had limited time to debug this yesterday but should hopefully have a resolution early next week.

Relevant

keystone/packages/core/src/admin-ui/utils/useAdminMeta.tsx

Line 74 in 1c187a8

gqlNames: getGqlNames({ listKey: list.key, pluralGraphQLName: list.listQueryName }), // TODO: replace with an object

Debugging showed me that the type of adminMeta is different - sometimes - I don't know why yet

[dcousens]

Likely some dependency has changed behaviour

[borisno2]

It looks like it has to do with a recent Apollo Client update. Adding

  "overrides": {
    "@apollo/client": "3.8.10"
  },

to my package.json fixed it for me.

Is has something to fetching the adminMetaData here

keystone/packages/core/src/admin-ui/utils/useAdminMeta.tsx

Lines 63 to 76 in b6f8657

	const adminMeta: StaticAdminMetaQuery['keystone']['adminMeta'] = adminMetaFromLocalStorage
	? adminMetaFromLocalStorage
	: data.keystone.adminMeta
	const runtimeAdminMeta: AdminMeta = {
	lists: {},
	}
	for (const list of adminMeta.lists) {
	runtimeAdminMeta.lists[list.key] = {
	...list,
	groups: [],
	gqlNames: getGqlNames({ listKey: list.key, pluralGraphQLName: list.listQueryName }), // TODO: replace with an object
	fields: {},
	}

where as @dcousens mentioned, adminMetaFromLocalStorage is different to data.keystone.adminMeta so on a 2nd pass through list.listQueryName, and others on the list object don't exist.

[LoganConnor44]

Is there any way to start project?

Without @borisno2 's override there is no way to start a project outside of using the other work-around that is mentioned indirectly which is using pnpm.

I tried on a prior application, multiple fresh installs, and a few dockerized environments - all with primarily npm and a few with yarn.

[dansp89]

When I put the 'pnpm-lock.yaml' from this repository, the project works fine.

It worked 100%, thanks!

[dcousens]

The problem is that @apollo/client isn't returning the expected data from useQuery, despite the request and response being well-formed.

I think I might pin us to "@apollo/client": "3.8.10" for now, until this can be resolved upstream.

[starblazingunicorn]

I have same problem :( nothing is helping. Any suggestions for a workaround?

[dcousens]

@starblazingunicorn have you resolved "@apollo/client" to "3.8.10"?
I am looking to make a patch for this tomorrow in any event.