When running npm run dev the following error shows up instead of starting the actual Ceramic stack.

> [email protected] dev
> node scripts/run.mjs

⠸ [Ceramic] Starting Ceramic node
[Ceramic] 
> [email protected] ceramic
> CERAMIC_ENABLE_EXPERIMENTAL_COMPOSE_DB='true' npx ceramic daemon --config ./composedb.config.json

✖ [Ceramic] Ceramic node failed to start with error:
✖ [Ceramic] npm

This is likely due to the script expecting ceramic to be exposed globally.

Background

Previously, I've run npm run dev successfully to do the entire workflow of the Create Ceramic App demo (i.e., update profile information, submit, do with another wallet, query via ComposeDB graphl query). However, for the past two days, I have not been able to do so successfully anymore, getting the following error.

For context, I'm loading this via Gitpod, although I've done it w/o any issues previously.

Steps to replicate

1. Go to https://gitpod.io/https://github.com/ceramicstudio/create-ceramic-app
2. Clone the template, install the deps, install @ceramicnetwork/cli globally (see #20) and run npm run dev
3. See error shown above.

Additional details

Sometimes I can import it manually via composedb composite:deploy src/__generated__/definition.json --ceramic-url=http://localhost:7007 --did-private-key=$(cat admin_seed.txt) but not always successfully (i.e., sometimes I get an ECONNREFUSED error as if the service were down). It would be interesting to figure out why that is the case.