Describe the bug
After upgrading to the v0.7.3, I found that the two.js was conflicted with the @types/two.js, and then I uninstalled the @types/two.js and used the
import Two from 'two'
, but two.makeXXX() or two.appendTo() method cannot be found in the two.module.d.ts, so these methods can't be used.
Ah shoot, sounds like the automated Typescript generator doesn't work too well. I'll have to continue to work on this. Thanks for reporting!
Unfortunately, in order to use this script it will take significant changes to the codebase. I think it would be better to generate the declaration file ourselves when the script generates the wiki documentation. This too, unfortunately, will take some time to get setup.
Sorry to be the bearer of this news.
Because of the semantics around how Two.js was originally wrote and how to get types declared properly, this issue relates to this issue in that there are number of stylistic changes the codebase could take in order to elegantly solve this issue.
I found a better library to convert JSDocs documentation into Typescript types. There are likely _a few_ rough edges still, but give the latest version a try: https://www.npmjs.com/package/two.js which is v0.7.4.
I tried installing the latest version but it seems like the types are missing from the npm package?

Sorry for the delay and thanks for sharing this @stefnotch. I'll update the NPM package today with the appropriate updates I just pushed to dev.
@stefnotch, types are now present in the NPM build. If you see issues with the types (which I'm sure there are, because i'm not a Typescript user!) please file a new issue. Thanks!