You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
currently we have to mix dependencies of all action providers to agentkit at package.json
e.g. you will need to install dependencies of twitter api even if your agent do not tweet and runs only morpho provider. This increase dev complexity with dependency hell of each package and also risks of package supply chain attack.
More obvious when you have different package each depends on viem, ethers-v5 or ethers-v6
Typical solution will be
a plugin systems with monorepo where each action has its own dependency (package.json), as in langchain / eliza
agentkit is a template, use cli to install only what is needed when you turn on a action provider (shadcn style)
End goal is only necessary packages end up in application agent's dependencies, within agentkit they stay as devDependencies or peerDependencies
wonder if related plans exists already?
Alternatives
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
🚀 The feature, motivation and pitch
currently we have to mix dependencies of all action providers to agentkit at package.json
e.g. you will need to install dependencies of twitter api even if your agent do not tweet and runs only morpho provider. This increase dev complexity with dependency hell of each package and also risks of package supply chain attack.
More obvious when you have different package each depends on viem, ethers-v5 or ethers-v6
Typical solution will be
End goal is only necessary packages end up in application agent's dependencies, within agentkit they stay as
devDependencies
orpeerDependencies
wonder if related plans exists already?
Alternatives
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: