@IvanH and anyone else who comes across this issue - I managed to solve the problem by using pnpm and following the instructions again from here: Ceramic configuration | ComposeDB on Ceramic
The issue with the GraphQL dependencies is still mentioned by pnpm however when running the script the GraphQL server starts without issue. The working package.json looks like this:
{
"name": "ceramic-composedb",
"version": "1.0.0",
"main": "index.js",
"license": "MIT",
"devDependencies": {
"@composedb/devtools": "^0.3.0",
"@composedb/devtools-node": "^0.3.0",
"@composedb/types": "^0.3.0",
"@types/node": "^18.8.2"
},
"dependencies": {
"@ceramicnetwork/http-client": "^2.5.0",
"@composedb/client": "^0.3.0",
"key-did-provider-ed25519": "^2.0.1",
"key-did-resolver": "^2.1.3",
"uint8arrays": "^3.1.0"
},
"type": "module"
}
Hopefully this will resolve the issue for you as well @IvanH if you haven’t fixed it already