-
Notifications
You must be signed in to change notification settings - Fork 155
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
What is the status of this repo? #23
Comments
markdown-it-katex is compatible with the latest KaTeX, the tests just aren't and |
There are 5 pending PR, one of them from June 2017. The code has not been updated for the last 2 years, 3 years for most files. There is a script injection issue that has been detected #26 @waylonflinn could you please let us know your thoughts on the repo status? @iktakahiro should we open issues on your fork instead? https://github.com/iktakahiro/markdown-it-katex/ |
For those of you using |
Glad you're all interested in the library. I intend to bring it up to date with the latest version. I'll carve out some time to work on this next week. |
@jbe456 thanks for your mention, I'd like to maintain my forked project https://github.com/iktakahiro/markdown-it-katex/ However, If this original package is upgraded, I think that is the best 👍 |
Hi All, note that there is a proliferation of In addition to this repo: Possibly because this repo wasn't maintained for a while. Might be worth trying to consolidate efforts if this repo gets going again. Note that they all seem to have an issue with |
@waylonflinn any news? (http://waylonflinn.github.io/markdown-it-katex/ made me laugh btw) |
@yakovlevkll (thanks, glad you liked it) |
FYI @everyone else - I've published the updated package to the NPM registry, so you can install it as |
@waylonflinn
This repo is no longer compatible with the latest versions of Katex - which means that it is necessary to use a forked update ala
@iktakahiro/markdown-it-katex
to get katex working as intended.Would it please be possible to clarify the status of the repo and whether there are plans to continue maintaining it? If no plans to maintain, whether it would be possible to cede the project to a new active maintainer, maybe @iktakahiro?
Given the name of the repo it would be opportune to keep this working, as this is the most apparent option when people are searching for
markdown-it
+katex
.Thanks.
The text was updated successfully, but these errors were encountered: