One note by the way. .use() does exist on frozen processors. It just always throws. Because of this I think this might be a good change, but I’m not 100% sure.

does exist on frozen processors. It just always throws

I think removing it from the typing is inline with the spirit of TypeScript.
For example, how TS handles objects

const a = {}

a.test
//^^^^
// Property 'test' does not exist on type '{}'.

.test throws a compile time error, even though one could access a.test and always get undefined.

edit:

we could add use with return type never in the FrozenProcessor typing https://mariusschulz.com/blog/the-never-type-in-typescript
I'm not sure it would add much benefit over not including use at all.

we could add use with return type never in the FrozenProcessor typing https://mariusschulz.com/blog/the-never-type-in-typescript
I'm not sure it would add much benefit over not including use at all.

I don’t think this adds much benefit.

Released in 9.1.0!