Converting to Typescript

[simenandre]

Hello,

I've been porting lambda-proxy-utils to Typescript. I was thinking of writing @types definitions, but this is such a nice little tool I'd rather see it being fully Typescript. As of right now, it has a few lint issues and a broken dependency (i think). There are also 13 @ts-ignore in the classes, those need to be looked at. I've used gts.

• Rebuild in Typescript
• Fix linting
• Fix type-is bug

I got carried away on the Response class, so all options are now written as one variable. We can revert back to the way @geoffdutton has done it. As of yet I have not submitted a pull request, since it's not perfect.

I changed from NPM to Yarn – not really a requirement either, i guess.

Have a look at bjerkio/lambda-proxy-utils.

Cheers!

[geoffdutton]

@cobraz I apologize for not paying attention to the Issues section. If you still have interest in this, I'd welcome a PR.

I'm thinking about create v2.0.0 which will drop support for Node 4, but this could also include changing it to typescript.

[hugoduraes]

@cobraz it'd be great to have the library in Typescript. Are you happy to create a PR as @geoffdutton asked? thanks :)

[simenandre]

Hello!

I can see what can be done :)

[simenandre]

I'm picking this up again!

[SimonJang]

Any update on this? If not, I wouldn't mind taking a look into it myself.