Welcome to the 🐸STT project! We are excited to see your interest, and appreciate your support!
This repository is governed by the Contributor Covenant Code of Conduct. For more details, see the CODE_OF_CONDUCT.md file.
If you have a feature request, then please provide the following information:
Is your feature request related to a problem? Please describe.
The current WASM bindings are written in JS and do not have type information, making it hard to work with in TS-based web projects.
Describe the solution you'd like
The generation of Typescript annotation/@types for the WASM JS APIs. This can happen either manually or, for example, generating them via JSDocs.
Describe alternatives you've considered
Do nothing :-) Folks can keep using the the APIs with no type hint, but that will make it hard to use in TS projects and more error prone.
Additional context
This came up a couple of times already in the coqui-STT Matrix channel.
Welcome to the 🐸STT project! We are excited to see your interest, and appreciate your support!
This repository is governed by the Contributor Covenant Code of Conduct. For more details, see the CODE_OF_CONDUCT.md file.
If you have a feature request, then please provide the following information:
Is your feature request related to a problem? Please describe. The current WASM bindings are written in JS and do not have type information, making it hard to work with in TS-based web projects.
Describe the solution you'd like The generation of Typescript annotation/@types for the WASM JS APIs. This can happen either manually or, for example, generating them via JSDocs.
Describe alternatives you've considered Do nothing :-) Folks can keep using the the APIs with no type hint, but that will make it hard to use in TS projects and more error prone.
Additional context This came up a couple of times already in the coqui-STT Matrix channel.