Rollup v3 support

[Mister-Hope]

https://github.com/rollup/rollup/tree/v3.0.0

├─┬ rollup-plugin-dts 4.2.3
│ └── ✕ unmet peer rollup@^2.55: found 3.0.0

packages/shared build: ./src/node/index.ts → ./lib/node/index.d.ts...
packages/shared build: (!) The "output.namespaceToStringTag" option is deprecated. Use the "output.generatedCode.symbols" option instead.
packages/shared build: [!] RollupError: Invalid value false for option "output.interop" - use one of "compat", "auto", "esModule", "default", "defaultOnly".
packages/shared build: https://rollupjs.org/guide/en/#outputinterop
packages/shared build: RollupError: Invalid value false for option "output.interop" - use one of "compat", "auto", "esModule", "default", "defaultOnly".

[Swatinem]

ah yes, the peer dependency says that the plugin is not (yet) compatible with rollup 3. Which is brand new I see ;-)

I believe node/npm changed the way they treat peerDependencies a while back, I will have to dig into how to properly use that.

[pi0]

There seems also some configuration updates. PR: #227

---

A really really ugly workaround for rollup@3 support in meantime:

    const dtsPlugin = dts(...)
    rollupOptions.plugins.push({
      ...dtsPlugin,
      outputOptions (...args) {
        const opts = dtsPlugin.outputOptions(...args)
        opts.interop = 'esModule'
        delete opts.namespaceToStringTag
        opts.generatedCode = { symbols: false, ...opts.generatedCode }
        return opts
      }
    })

[nicolas377]

There isn't really a workaround needed for v3 support for right now. Rollup only reports a warning, and the outputted code isn't affected. Obviously, the PR should still be merged. Just putting this out there for onlookers.

[Mister-Hope]

Rollup only reports a warning, and the outputted code isn't affected.

why am I unable to have it work? From the log I provided, rollup gives an error with output.interop. (I haven’t tested with later v3 yet, is this changed?)

[nicolas377]

That's weird. I used rollup-plugin-dts 4.2.3 with rollup 3.1.0 and npm i --force and it worked just fine.

[Swatinem]

Just published 5.0.0 which supports/requires rollup 3, and also raises the minimum supported node version to 14.