Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Distribute typescript definitions
See original GitHub issueIs your feature request related to a problem? Please describe.
When using katex in typescript, one has to use the @types/katex package to get some type interference. However, these type definitions are quite minimal.
Describe the solution you’d like: Provide full typescript definitions automatically.
Describe alternatives you’ve considered:
Using @types/katex.
Additional context: https://www.typescriptlang.org/docs/handbook/declaration-files/publishing.html
Issue Analytics
- State:
- Created 2 years ago
- Comments:6 (5 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
The @types/katex type definitions seem completely broken. Katex as of v0.15 seems to have only a default export, so I have to
import katex from 'katex'. But the type definitions demand that Iimport * as katex from 'katex', which is completely different.Thanks for the pointers and suggestion. Here are the
@types/katextype definitions.An advantage of publishing them ourselves is we can update them together with KaTeX versioning (though it’s pretty rare for them to change, we might add an option or two). Overall it seems like a good idea, related to #2110.