Add Typescript support to Node SDK
## Description Add typescript support to Node SDK. ## Reason Currently the Node SDK has 0 type support and make developer experience tough when building an app with typescript and trying to use the SDK it would be nice to be able to see what an expected response would be in the code editor. This also causes responses to be typed as `any` which isnt quite right since we can see the types in the documentation  ## Solution We currently use `npm i amadeus --save` to install the SDK. Adding something like `npm i --save-dev @types/amadeus` would be amazing
Posted by WillGarman on Mar 21, 2024, 7:12 AM
Tags
Related issues
- As I replied in another comment[1], it's their software, their choice.
- [Feature] Support external model integration via personal API keys and local LLMs (BYOK)
- > So when head of companies don’t care about quality, they’ll push hard no matter what to have speed.
- Feature request: support multiple named accounts per app/connector
- Support standalone Windows installer (`codex-setup.exe`)
- [feature]: Move OIDC back to self-hosted OSS(Plane Free)
Raise real-world problems, find people facing the same issue, and discuss solutions.2,000 issues0 comments
support (SaaS)
As I replied in another comment[1], it's their software, their choice.
[Feature] Support external model integration via personal API keys and local LLMs (BYOK)
> So when head of companies don’t care about quality, they’ll push hard no matter what to have speed.
Feature request: support multiple named accounts per app/connector
Support standalone Windows installer (`codex-setup.exe`)
[feature]: Move OIDC back to self-hosted OSS(Plane Free)
I was running about 1000 machines on VMware in my previous career.
libpdfiumandroid.so not 16 KB aligned – Google Play 16 KB page-size requirement
Add Typescript support to Node SDK
## Description Add typescript support to Node SDK. ## Reason Currently the Node SDK has 0 type support and make developer experience tough when building an app with typescript and trying to use the SDK it would be nice to be able to see what an expected response would be in the code editor. This also causes responses to be typed as `any` which isnt quite right since we can see the types in the documentation  ## Solution We currently use `npm i amadeus --save` to install the SDK. Adding something like `npm i --save-dev @types/amadeus` would be amazing
Comments (0)
No comments yet. Start the discussion.