Yeah, we don’t have full types for libSquoosh yet, only for some of the files. It’s an incremental migration that @ergunsh is working on :)

Bump, trying to use this to replace imagemin with TypeScript, but it doesn't have types so I can't even IntelliSense what options/properties are available.

That’s more a question of documentation than TypeScript tbh. Feel free to take a look at the options object in codecs.ts.

Having a list of properties/arguments (that work with IntelliSense) and their types is sorta documention, but also one of the purposes of TS. Some even go as far as adding a description to everything, making it even more like a built-in documentation.

Linking to that specific object does help way more than what's currently in the docs though.

Yeah, we know documentation is a weak point and we are working on that. Fwiw, we do link to codecs.ts from the README of libsquoosh.

@ergunsh Thoughts on this one?

I think we can do something like tsc --declaration --emitDeclarationOnly --declarationDir build to generate the .d.ts files and publish those to npm.

Totally @styfle! :)

I was a bit skeptical to expose the types before improving the type definitions for preprocess and encode functions since those take some complicated parameters and providing ts types without them felt a bit meaningless.

So, I created a PR to add the parameter types to those #1141 and created another PR to expose the types #1142