fix(pack): replace "tsdown" with "vp pack" in error messages

[fengmk2]

Add brandTsdown() build-time patching to replace upstream "tsdown"
branding in the bundled error message when no input files are found.

Follows the same post-build branding pattern as brandVitest().

[fengmk2]

• feat(pack): add --exe flag and upgrade tsdown to 0.21.0-beta.2 #646
• fix(pack): replace "tsdown" with "vp pack" in error messages #642 👈 (View in Graphite)
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[cpojer]

Wowza this is shaky.

Can we not instead do something like setting an env var if tsdown is run in a Vite+ context (or any other way of passing config to tsdown), and change the printing in tsdown based on whether the env var is set?

[fengmk2]

Wowza this is shaky.

Can we not instead do something like setting an env var if tsdown is run in a Vite+ context (or any other way of passing config to tsdown), and change the printing in tsdown based on whether the env var is set?

Yes, it currently seems that any upstream code changes will cause string replacement failures. However, the good news is that the dependency auto-upgrading GitHub Action will handle the failure logic via Claude Code, which will attempt to automatically update these replacement logics. https://github.com/voidzero-dev/vite-plus/blob/main/.github/workflows/upgrade-deps.yml

I will create a follow-up issue after the Alpha release, especially after we have open-sourced it, to propose a CLI brand word replacement solution to upstream projects like Vite, tsdown, oxc, etc.

[fengmk2]

Merge activity

• Feb 27, 2:39 AM UTC: Graphite rebased this pull request as part of a merge.
• Feb 27, 5:26 AM UTC: @fengmk2 merged this pull request with Graphite.