keystone.getResolvers is not a function

NOTE: I notice there have been some changes in the last day to the Keystone repo, so perhaps when I reinstalled my node_modules it grabbed the latest version and that is causing the problem?

I’m working on a KeystoneJS project. I added hooks to one of my lists and the project worked fine. When I was finished with my work I pushed my work to GitHub and made a pull request for my team. However GitHub complained about a security error (in yarn.lock), so I deleted yarn.lock, reinstalled node_modules(yarn). When I ran the project again locally, however, I received the following error:

✔ Validated project entry file ./tsout/index.js
✔ Keystone server listening on port 4545
✔ Initialised Keystone instance
✖ Connecting to database
TypeError: keystone.getResolvers is not a function
    at createApolloServer (/Users/r/Documents/projects/yaa-keystone/node_modules/@keystonejs/app-graphql/lib/apolloServer.js:148:25)
    at GraphQLApp.prepareMiddleware (/Users/r/Documents/projects/yaa-keystone/node_modules/@keystonejs/app-graphql/index.js:23:20)
    at /Users/r/Documents/projects/yaa-keystone/node_modules/@keystonejs/keystone/lib/Keystone/index.js:752:17
    at Array.map (<anonymous>)
    at Keystone.prepare (/Users/r/Documents/projects/yaa-keystone/node_modules/@keystonejs/keystone/lib/Keystone/index.js:751:12)
    at executeDefaultServer (/Users/r/Documents/projects/yaa-keystone/node_modules/@keystonejs/keystone/bin/utils.js:112:42)
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

It’s throwing the error deep inside the keystone package in node_modules. I deleted and reinstalled node_modules, I reverted my project to a commit from yesterday that worked fine, but I keep getting the same error.

I went back to the already-working ’develop` branch and the same issue. It must be something inside node_modules?

Any help appreciated, as I’m dead in the water now.

[jesstelford]

You’re correct; this was changed in a release that went out about 10hrs ago.

There’s a chance that the version of @keystonejs/keystone your project depends on is different to the version which @keystonejs/app-graphql depends on. If that’s the case, then this error will occur.

You could verify this with yarn:

yarn why @keystonejs/keystone

Ideally, that would show only one version, but I suspect it will show you two versions.

By removing your yarn.lock, yarn has been instructed to fetch the latest versions of packages, and led to this issue. It’s generally a good idea to avoid removing yarn.lock in its entirety for this and similar reasons. (Personally, I do still delete it sometimes as it’s the only way to get certain things to happen).

Two possible solutions to your current problem:

1. Revert the changes in yarn.lock, remove your node_modules folder, and run yarn again.

   • If this continues to throw errors, go through your keystone dependencies in package.json, and remove any semver range specifiers, then re-run yarn For example, make this change:

   -  "@keystonejs/keystone": "^1.0.0",
   +  "@keystonejs/keystone": "1.0.0",
   

   This should lock down the versions

2. Preferred. Use ~yarn outdated --latest~ yarn upgrade-interactive --latest to update to the latest versions of all @keystonejs/* packages.

   • While there are some breaking changes, they’re mostly for obscure undocumented functions, so you should be fine to do a full update as long as you’re not too far behind.
   • Every package has a detailed changelog which you can find either within the repo (eg; https://github.com/keystonejs/keystone/blob/master/packages/keystone/CHANGELOG.md), or by using the changelogs.xyz tool (eg; https://changelogs.xyz/@keystonejs/keystone)

[jesstelford]

Really sorry about the headaches this has caused you!