fix: add param names to jsdocs, remove types separation

[KuNman]

Hey,
while we tried to use this library discovered that there are small issues with type declarations:

1. Few typescript types miss names for variables as they are missing in jsdocs.
2. We couldn't use library as typescript types were exported to separate directory, while usually they are alongside source code (commonJS).

PR fixes both issues.

[szaldivar]

this is needed for ES6 modules (importing modules with the modern syntax import ... from. Are we sure we want to revert to CommonJS (commonJS is not supported in browsers and is generally considered that new projects should use ES6)

[KuNman]

Let me verify is it still needed.

[KuNman]

@szaldivar yes, we still need it to use with import {} from....

[szaldivar]

Hey, while we tried to use this library discovered that there are small issues with type declarations:

1. Few typescript types miss names for variables as they are missing in jsdocs.

2. We couldn't use library as typescript types were exported to separate directory, while usually they are alongside source code (commonJS).

PR fixes both issues.

What did you run into when using the library?

[KuNman]

Hey, while we tried to use this library discovered that there are small issues with type declarations:

1. Few typescript types miss names for variables as they are missing in jsdocs.

2. We couldn't use library as typescript types were exported to separate directory, while usually they are alongside source code (commonJS).

PR fixes both issues.

What did you run into when using the library?

We are using it for node backend with nestjs.

[FedericoTartarini]

Thank you @szaldivar for commenting and reviewing the Pull request. I will leave it with you since you have a deeper understanding of the topic.