Lee Langley

> And it only fixes that one file ... > > Adding the following (and a couple variations) in FudgeDice.js doesn't resolve the issue there. > > ```js > /**...

Hmm,. I'm not sure that it works correctly either. I've just checked your `Engine` one: ```javascript /** * @typedef {import("random-js").Engine} Engine */ ``` And it produces the following: ```typescript export...

Thanks for those links! From that I've also found the it actually documented on the Typescript site: https://www.typescriptlang.org/docs/handbook/jsdoc-supported-types.html#import-types (Same page I was looking at before, but further down).

I've realised that using the `@typedef` method seems to cause the documentation generation (`npm run build:docs`) to fail, for some reason. I've not managed to get an error response from...

I thought I'd take a look at this from a different angle. I've been playing around with seeing what actually happens with the circular dependencies. Instead of adding the `@typedef`...

I've been looking at this again recently, and have had some success with custom bundling MathJS. Part of the issue was that both MathJS and random-js were being bundled into...

Nice! Thanks for testing it. Can you confirm that it's all still working for you? Also, what are you using to check the file sizes? It looks really handy.

Just a note on my thoughts at the moment: We can probably achieve this in a similar way to the RNG, where we have a separate class that you can...

Does this PR resolve the issues on Linux and, if so, is it likely to be merged in at some point? It would be really nice to have a media...

I think you're correct about the lack of file extension; browser environments expect the full path and filename. Is there a way you could tell Gulp to add the `.js`...