mdx-js
mdx-js and TypeScript: What are the blockers from it from being rewritten in TS? #1540
-
|
Where does TypeScript stand with mdx-js 2.0 and beyond in the here and now? The last mention is #1041, for 2.0, @ChristianMurphy introduced typings in #1078/#1079. This is exciting news! What's keeping an even bigger change, e.g. full rewrite in TS from happening? What effort would that actually entail? The complexity of the types involving a lot of generics potentially? This would be invaluable since it offers extra safety/completions when extending MDX. From experience I highly prefer pure TS to generated or handmade typings. Do maintainers or contributors have enough spare time to rewrite in TypeScript if they were funded? If so is there a ballpark of how much they'd want raised? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
|
Unified, the underlying library supporting remark and mdx is in the process of adding native typings through TypeScript+JSDoc (see unifiedjs/rfcs#5, unifiedjs/unified#121, and https://www.typescriptlang.org/docs/handbook/jsdoc-supported-types.html for more info). There may be interest in bringing it to MDX 2 as well. |
Beta Was this translation helpful? Give feedback.
Unified, the underlying library supporting remark and mdx is in the process of adding native typings through TypeScript+JSDoc (see unifiedjs/rfcs#5, unifiedjs/unified#121, and https://www.typescriptlang.org/docs/handbook/jsdoc-supported-types.html for more info).
Financial support to fund the effort is welcome! (https://opencollective.com/unified)
There may be interest in bringing it to MDX 2 as well.
Though disagreements around some of the planned features for version 2 have stalled new features and the GA release for a while.
Hopefully it can make it's way into MDX. In the meantime XDM (https://github.com/wooorm/xdm) offers another option, with native TS+JSDoc typings already provided.