Corrupted declarations when re-exporting nested modules

[Danielku15]

Describe the bug

I am trying to re-export the types from my individual modules on the top level bundle module. This works fine for typescript when importing the namespaces and types.

But the DTS generated by this plugin via rollupTypes get corrupted on subsequent builds.

Reproduction

https://stackblitz.com/edit/vitejs-vite-zqiicdze

Steps to reproduce

• npm run build
• Inspect dist/index.d.ts which contains a proper namespace and exports for the re-rexported module:

declare class Class1 {
}

export declare namespace module {
    export {
        test1,
        Class1
    }
}

export declare function test(): void;

declare function test1(): void;

export { }

• run again npm run build
• Inspect dist/index.d.ts again and notice the corrupted declaration

export declare namespace module {
        {
        test1,
        Class1
    }
}

export declare function test(): void;

export { }

• delete the dist folder and run npm run build again
• Notice again the proper definitions.

System Info

System:
    OS: Linux 5.0 undefined
    CPU: (8) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
    Memory: 0 Bytes / 0 Bytes
    Shell: 1.0 - /bin/jsh
  Binaries:
    Node: 18.20.3 - /usr/local/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 10.2.3 - /usr/local/bin/npm
    pnpm: 8.15.6 - /usr/local/bin/pnpm
  npmPackages:
    vite-plugin-dts: ^4.5.0 => 4.5.0

Validations

• Read the FAQ.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• The provided reproduction is a minimal reproducible example of the bug.

[qmhc]

You should empty dist before each build, because rollupTypes base on the files in output dir.

[Danielku15]

This defies the whole purpose of incremental builds and caching. Always doing full re-builds to get non-broken outputs is not really a feasable solution to this problem.