Using --deps.onlyBundle without a value should assume an empty array or "true"

[will-stone]

Hi,

Currently using --deps.onlyBundle CLI flag causes an error:

TypeError: Expected pattern to be a non-empty string

However, this flag is useful for determining if the package.json dependencies is set up correctly (rather than just ignoring all bundling). Which means it needs to be set up using --deps.onlyBundle='()' or --deps.onlyBundle=null or --deps.onlyBundle=true to get the errors about which deps would have been bundled.

I understand this can be set to an empty array in tsdown.config but how about defaulting --deps.onlyBundle to true? This would follow the CLI Flag Patterns where

--foo sets foo: true

Thanks,

Will.

[sueun-dev]

quick repro says the bare positive flag is the broken path here.

I tested tsdown@0.22.2 in a tiny fixture with left-pad as a bundled devDependency. Default build warns, --deps.onlyBundle=left-pad succeeds, but --deps.onlyBundle fails with TypeError: Expected pattern to be a non-empty string. In current main (9f05179), the CLI allows unknown dotted flags, then resolveDepsConfig() turns non-false onlyBundle into toArray(onlyBundle), and the deps plugin passes that into matchPattern()/picomatch.

So #884 covers "CLI flag exists", but this exact bare positive form still needs either a boolean branch or docs saying only valued patterns / --no-deps.onlyBundle are supported.

[will-stone]

--no-deps.onlyBundle doesn't block deps from being bundled, in fact it removes the "Detected dependencies in bundle" hint from the CLI output.

It would be handy if --deps.onlyBundle defaulted to [] so that it's possible to mimic config file settings with CLI flags 🙏 🙂