By default tsup bundles all import-ed modules but dependencies and peerDependencies in your package.json are always excluded.
So, I would think that if peerDependencies are always excluded, then if I specify a dependency in both devDependenciesandpeerDependencies (meaning, it's a peer dependency, but when I'm working on developing the package, I also want it to be installed), then it should not be bundled.
But, this is not the behavior I am seeing. Instead, the dependency is bundled into the build, unless I explicitly add it to externals. Is this intentional, or a bug? If it's intentional, maybe the README can be clarified to avoid such confusion?
Upvote & Fund
We're using Polar.sh so you can upvote and help fund this issue.
We receive the funding once the issue is completed & confirmed by you.
Thank you in advance for helping prioritize & fund our backlog.
According to the readme:
So, I would think that if peerDependencies are always excluded, then if I specify a dependency in both
devDependenciesandpeerDependencies(meaning, it's a peer dependency, but when I'm working on developing the package, I also want it to be installed), then it should not be bundled.But, this is not the behavior I am seeing. Instead, the dependency is bundled into the build, unless I explicitly add it to
externals. Is this intentional, or a bug? If it's intentional, maybe the README can be clarified to avoid such confusion?Upvote & Fund