Kricsleo

Please provide a minimal reproduction 🙏🏻. Maybe you don't export thoes types. This plugin works like tree-shaking in ES modules, removing types that are not exported.

I believe that's the expected and standard behavior: users can only import what you explicitly export, correct? 🤔 It's like defining two functions: ```ts function private() { ... } function...

Implicitly adding "export" may cause export duplicate name conflicts. ```ts type Child = string export interface Public { child: Child } type PublicChild = number export { PublicChild as Child...

I tested your reproduction—both `nitro build` and `nitro dev` worked without errors. Could you describe how to reproduce the issue? 🙏

This issue has been resolved in [rou3](https://github.com/h3js/rou3). `h3@1` uses an older version of `rou3` (previously named `radix3`), but the upcoming `h3@2` addresses this by upgrading to the latest `rou3`.

Do you mean a stricter isLogObj function check, requiring `date` to be `Date` if it exists? https://github.com/unjs/consola/blob/5ac9ed76b021c9ffc768f0727355238056aabeb1/src/utils/log.ts#L16-L33

#379 makes the runtime check more strict. Personally, I prefer stricter types that align with runtime behavior. This can improve DX 😃 (I've also simplified the `LogParam` for better understanding...

So you're suggesting we remove the runtime behavior as well as the types? 🤔 (Regardless, it's better to align the runtime behavior with types.)

Adding `name` in entries can additionally change the output path. In your example config: ```ts export default defineBuildConfig({ entries: [ { input: "src/proxies/index", // ↓ Add "name" to specify the...

PRs are more than welcome! ❤️