dependency management in public packages

[stefanofa]

while looking at the source code of the monorepo, I noticed something interesting, eg. some dependencies aren’t listed in the packages itself but are marked as external in the tsup config.

for example, the agents-sdk package doesn’t declare ai, @ai-sdk/react, or react as dependencies, even though they’re used in the code. instead, the built ES modules keep them as external imports instead of bundling them. that makes sense, but I’m wondering if it’s the best approach.

I assume the idea is to let users install only the dependencies they actually need, for example, skipping react if they don’t use it. but doesn’t this make it harder to control dependency versions and compatibility? wouldn’t it be better to list them as peerDependencies instead? and if that’s the case, it would probably be safe to just remove them from external in tsup config, since by default tsup automatically excludes packages specified in the dependencies and peerDependencies.

also, in the hono-agents package, agents-sdk and hono are both listed as peerDependencies and devDependencies. wouldn’t it make more sense to pick just one? or maybe even declare them as regular dependencies?