)

Co-authored-by: autofix-ci[bot] <114827586+autofix-ci[bot]@users.noreply.github.com>

Co-authored-by: Kevin Deng <[email protected]>

…917)

…oks (#918)

* feat(plugin): add `tsdownConfig` and `tsdownConfigResolved` plugin hooks

Introduce two tsdown-specific per-plugin lifecycle hooks modeled on Vite's
`config` and `configResolved`:

- `tsdownConfig(config, env)` — called before the user config is resolved.
  May mutate in place or return a partial `UserConfig` to be deep-merged.
- `tsdownConfigResolved(resolvedConfig)` — read-only notification fired once
  per produced `ResolvedConfig` (per output format).

Both hooks are detected on user plugins via duck-typing, so existing
Rolldown plugins continue to work unchanged. A `TsdownPlugin` interface,
`TsdownConfigEnv` interface, and `flattenPlugins` helper are exported
from `tsdown/plugins`.

* refactor

* refactor(plugin): simplify `TsdownConfigEnv` to only `inlineConfig`

`watch` and `cwd` are already reachable via the first `config` argument
passed to `tsdownConfig`, so keeping them in env duplicates data and risks
going stale. Drop both — `inlineConfig` remains because it is the only
piece of context that cannot be derived from `UserConfig`.

* refactor(plugin): replace `TsdownConfigEnv` with `InlineConfig`

The env object only wrapped a single `inlineConfig` field, so pass the
`InlineConfig` directly as the second argument instead. Drops the
`TsdownConfigEnv` interface and its re-exports.

* feat(plugin): add `TsdownPluginOption` type

Mirrors Rolldown's `RolldownPluginOption` but with `TsdownPlugin` as the
atom, so that `UserConfig.plugins` entries get proper type-checking for
the new `tsdownConfig` / `tsdownConfigResolved` hooks.

* fix

* update

* refactor

…919)