According to the readme:
By default tsup bundles all import-ed modules but
dependencies
andpeerDependencies
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 devDependencies
and peerDependencies
(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?
Pay now to fund the work behind this issue.
Get updates on progress being made.
Maintainer is rewarded once the issue is completed.
You're funding impactful open source efforts
You want to contribute to this effort
You want to get funding like this too