Suggestion: Check about tpescript is right or wrong in .d.ts files.

[linbingquan]

I think we need a tool, like tsc. Sorry I don't know how to do it...

[Mugen87]

The project is already doing this. Checkout how tsc is used in test-lint.

three.js/package.json

Line 56 in b4473c2

"test-lint": "eslint src --ext js --ext ts && tsc -p utils/build/tsconfig.lint.json",

[linbingquan]

The project is already doing this. Checkout how tsc is used in test-lint.

three.js/package.json

Line 56 in b4473c2

"test-lint": "eslint src --ext js --ext ts && tsc -p utils/build/tsconfig.lint.json",

Thank you for your reply. I tried this script npm run test-lint, it doesn't work very well, it can't found any error/warning. May be I missed something.

[Mugen87]

It works well on my system. Besides, I'm not sure why you refer to #11552. The discussion about TypeScript in this issue was off-topic and unrelated to ES6 classes.

[linbingquan]

It works well on my system.

On my system is:

I'm not sure why you refer to #11552. The discussion about TypeScript in this issue was off-topic and unrelated to ES6 classes.

I am sorry, I deleted the related comment, It didn't unrelated with #11552

[Mugen87]

Well, right now the command does not produce an output since everything is clean. If you for example remove an import in a d.ts file, a respective error should be reported.

[donmccurdy]

Note that the tsc command is looking at the example and unit test code, and comparing that against the type definitions, to ensure that these uses of the three.js APIs match the uses that the type definitions would allow. This will catch many issues, but not all issues — it cannot guarantee that the type definitions match the actual JS source code completely.

Unfortunately, the TypeScript project has not provided any robust way to compare d.ts type definitions to JavaScript source code to detect mismatches more directly.