-
Notifications
You must be signed in to change notification settings - Fork 4.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
After running Pnpm start #3151
Comments
Hello @SnoochiMink! Welcome to the elizaOS community. Thank you for opening your first issue; we appreciate your contribution. You are now an elizaOS contributor! |
Try pulling the latest code. This PR should fix it: #2901 |
I was having this issue the other day, I think it ended up being to do with the version of Node I was running |
Additionally, make sure to delete your node modules first then reinstall if still doesn't work.
|
You can contact me there on my gig I will help you out! |
Imagine using a debugging forum of an open-source community-built project to charge people to fix their issues 💀 |
pnpm -v 10.0.0
nvm -v 0.40.1
node -v v23.3.0
Installed all prerequisites and dependencies correctly
'pnpm install --no-frozen-lockfile'
got this after install:
decided to run build anyways
'pnpm build'
Ran pnpm start and got this error:
![Image](https://private-user-images.githubusercontent.com/192313172/408846827-a2be968a-44a6-474b-9f17-1690919979da.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MzkyNjE5MzksIm5iZiI6MTczOTI2MTYzOSwicGF0aCI6Ii8xOTIzMTMxNzIvNDA4ODQ2ODI3LWEyYmU5NjhhLTQ0YTYtNDc0Yi05ZjE3LTE2OTA5MTk5NzlkYS5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjUwMjExJTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI1MDIxMVQwODEzNTlaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT1jMWEyY2JlY2Y1MzJhZTMzYWU4ZGJkNjM3YTVmYmQxNGQxNDA4ZTY3YjA1MDM3MzliOTY0N2ZkNGNmNjcyNDY2JlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCJ9.q-F2w-65JRdPAxJiKFW_SSqV2bEIua1N9fLMQpPegxY)
The text was updated successfully, but these errors were encountered: