-
Notifications
You must be signed in to change notification settings - Fork 60
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
docs: add eliza tutorial #1209
base: main
Are you sure you want to change the base?
docs: add eliza tutorial #1209
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
||
## Quickstart | ||
|
||
Please follow the [Quickstart Guide](./index.md) to set up your development environment. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Love the reuse/single source of truth!
Add the plugin to agent's `package.json` | ||
|
||
```bash | ||
pnpm add @elizaos-plugins/plugin-foo@'workspace:*' --filter ./agent |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No need for changes now, but we need to agree on a package manager and use it consistently.
I can't see how this would be the case, but if this won't work with yarn or npm, I'd add pnpm as a prereq.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is project-related, and Eliza enforces only-allow
pnpm
.
By the way, both npm and yarn are actually quite outdated.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great tutorials! Added a few suggestions and some minor change requests to bring them inline with the other tutorials.
…nings and capabilities
Co-authored-by: Brian Doyle <briandoyle81@gmail.com>
Co-authored-by: Brian Doyle <briandoyle81@gmail.com>
Co-authored-by: Brian Doyle <briandoyle81@gmail.com>
No description provided.