[Not Done] Add JSDoc typing

[DrJKL]

Addresses #1

Not done. I'll wait to see if @shanewholloway is okay with this direction.

Questions

• Is seed always expected to be a string?
• What should state be?
• Should xg just be {next(): number;}?
• What all opts are there? (I can just go through the code and find uses when I have some free time this week)

[shanewholloway]

From a short review, this approach takes a dependency on TypeScript (in package.json), transforming the project into a TypeScript based-project. I'd prefer not to do this, if practical. How does the .d.ts sidecar information get bundled under Rollup into the published esm/ directory?

The Typed JavaScript JSDoc approach seems workable, if verbose, and sidesteps a dependency on TypeScript. It may also adds some direct value for those browsing the source code directly in node_modules/ or GitHub.

Regarding your listed questions, if I once knew, that cache has long been cleared! 😅
My intent, as I remember, was for this project to be as close to a direct port to ESM as feasible, and to maintain 1:1 reproduction of each function's outputs given the same inputs. The test suite can act as guide to some of the parameters. I don't remember if the test suite used every API interface afforded by the original seedrandom module. That will likely require an audit/review of the code, as you propose in the last question bullet.