ERR_PNPM_RECURSIVE_RUN_FIRST_FAIL
Describe the bug
ERR_PNPM_RECURSIVE_RUN_FIRST_FAIL @elizaos/[email protected] start: node --loader ts-node/esm src/index.ts "--isRoot"
Exit status 1
Hello @TobiGoldD! Welcome to the ai16z community. Thank you for opening your first issue; we appreciate your contribution. You are now a ai16z contributor!
Are you trying to run in windows environment? Error might or might not be related to the windows environment but if are on Windows, you will need WSL anyway, try to run it in that.
Please use node version 23.3. And remove node_modules then, pnpm i again.
23.3 is not availible on their web site also this was working for about 6 hours before suddenly stopping with the error
What is error, please share screenshot here. Note for Windows Users: WSL 2 is required.
that is the error that comes up when i run pnpm start or npm start
Same problem in MacOS
I run on Apple Silicon with no issues. Can you all try run the ElizaOS not the starter (in case it was the starter) and send me a feedback please ?
Downgrade your node to exactly 23.3.0 and follow the docs to do a fresh setup.
hi are you already fix this error? i have same problem
sudo apt-get install build-essential run this command on linux
I have the sama issue :/ Did someone find a solution?
I have the sama issue :/ Did someone find a solution?
Yes Try to checkout the last release Has been solved on the last one
I've had the same issue on macOS. Checking out on latest release alone didn't solve my issue (maybe because i was adding API_KEY only in defaultCharacter.ts). These are the steps i've gone through: Clone Eliza repo -> Make sure you use node v23.3.0 -> Checkout to latest release -> Copy .env-example into .env -> Make sure you have API_KEY in your env and change the modelProvider if you need to -> pnpm i && pnpm build && pnpm start
Not sure if node v23.3.0 is essential, but it throws out warning unless you use it.
I have the same issue, did anyone find a solution to the issue?
I have the same issue, did anyone find a solution to the issue?
@purpleethereum solutions seems to work @zubyoha