TypeScript declaration files are supported by many IDEs, which can provide type checking and autocomplete for user scripts. An example of a supporting IDE is VSCode.
Hi @Sportzpikachu, thanks for taking the time to report this and welcome to Wikimedia Phabricator!
Unfortunately this Wikimedia Phabricator task lacks information.
If you have time and can still reproduce the situation: Please add a more complete description to this task.
That should be a specific example, basic context (what are "Typescript typings"? link welcome), and a use case.
You can edit the task description by clicking . Ideally, a good description should allow any other person to follow these steps (without having to interpret steps) and see the same results. Problems that others can reproduce can get fixed faster. Thanks again!
Unfortunately closing this Phabricator task as no further information has been provided.
@Sportzpikachu: After you have provided the information asked for and if this still happens, please set the status of this task back to "Open" via the Add Action... → Change Status dropdown. Thanks!
I did take a look at types-mediawiki but it didn't quite cover the interfaces in Vector and WikimediaEvents hence this publish - I'd imagine eventually we'd want a @wikimedia scoped npm package.
The frontends standards group is a more appropriate tag here to work out who's using TypeScript, what the needs are, communicate this issue more broadly and find a common solution.
I looked over the two "prototypical implementations" mentioned in the task description now but they're bare-bones. Types-mediawiki is quite well-developed (even mw.config is typed thanks to this PR) A few obscure interfaces like mw.experiments aren't there, but can be easily added. @Jdlrobson Do you want to move this repo over to the wikimedia github organization? Then I suppose we can have it published under the wikimedia npm organization as well. I feel this would simplify matters for the wikimedia projects wishing to use TypeScript.