Add a Typescript declaration file

[Electroid]

Closes #6 by adding a Typescript declaration file.

[mhart]

Oh awesome! Thanks, I'll have a look at this sometime in the next couple of days

[Electroid]

Alright, removed the declaration tag at the top, and rebased to the current master!

[Electroid]

@mhart Okay to merge? 😄

[trjstewart]

Hey @mhart any chance of getting this merged?

[blakeembrey]

@mhart Happy to be a resource to help keep this maintained. I've been using this definition since last last year without issues.

[sodabrew]

Likewise, I was excited to see this referenced in the recent Cloudflare blog post, and am using these TypeScript definitions.

[mhart]

Hey all – sorry for the radio silence – tough times.

I actually wanted to get this happening with JSDoc comments, but I got sidetracked.

I'll get this in and then move to that – thanks!

[mhart]

Released as 1.0.6 – thanks again @Electroid for the contribution 🙌

[sodabrew]

Woo! Thank you @mhart!!

[donocode]

I might have done something wrong but when I copied these types into my project I had to rename AwsSigner to AwsV4Signer as that's the name of the exported class

[mhart]

I ended up implementing the JSDoc solution and have republished the types in 1.0.7

Let me know if there are any problems!

[blakeembrey]

@mhart The new version doesn't work because it's being wrapped in declare module, it can't be within a declare module to be imported:

aws4fetch/dist/aws4fetch.d.ts

Line 1 in 37311c5

declare module "main" {

[mhart]

Ugh, yeah the module name is a problem. Pity typescript didn't pick that up from any of the tests within the repo itself.

Thanks for the PR @blakeembrey – this has been fixed in v1.0.9

[jivan99]

@mhart
The types field in package.json is no longer used if there is an exports field. This is causing unresolved type declarations.
TS Doc Reference

I have created a PR #60 to fix the issue.