Best way to export interfaces for a module that only has a default export

[typings]

Best way to export interfaces for a module that only has a default export

[blakeembrey]

Is this frowned upon because it pollutes the environment with a namespace that the consumer may not be expecting?

Yes.

Any other thoughts or good ways to do this?

If this is ES6 style with a default export, do how it currently is. Just export alongside the default export. Also, the syntax you're using could be simpler since it's an ES6 import: import Griddle, { CustomColumnComponentProps } from 'griddle-react'. That's what I would normally do, there's no namespacing issues and it's all on the users to do what they want. Does that help?

For ES5/CommonJS modules using module.exports, the type definition is usually a slightly different but similar pattern using a namespace.

declare function main (options: main.Options): void;

declare namespace main {
  export interface Options {}
}

export = main;

[hodavidhara]

Ah I had forgotten about the syntax that allows for both default and destructuring, that does make it nicer! I guess I didn't like it because it seems a little misleading to look like you're importing something that doesn't actually exist in the library and is purely defined in the typings, but I guess there is no getting around that.