fix: represent export correctly in types

[G-Rath]

The current types are incorrect because this plugin is exported using module.exports which is not equivalent to export default; while TypeScript handles this under the hood for native TS files (which is why those don't error), attempting to use this module with require in JS files checked by TypeScript will result in an error:

This is because TypeScript expects such modules to be exporting a default property that should be used in CommonJS, so instead it wants us to do { default: RemoveEmptyScriptsPlugin }:

This property does not actually exist at runtime though:

Instead, the correct way to type a module.exports based export is to use export =, and then to use a namespace to export additional types and interfaces (as there can only be one top-level export).

[webdiscus]

@G-Rath

Thank you!