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
Fails with marked-1.1.0 #28
Comments
Hello, thanks for that report. Will look into it. Ping me in a week or so if i forgot. |
ping |
Yep, sorry, fixing this is not that easy and i got busy. Will try again later, but keep pinging ! |
I tried using Selective dependency resolutions but that failed as well:
Can you please make |
@kapouer - Thank you for this package. Pinging you for a fix of this package so that we can upgrade to Thank you. |
marked is now at V1.2.0 but then will marked-man use the newer versions? |
Failure with marked-1.2.7:
|
Ping again, will this be fixed any time? |
@kapouer - Would making a donation through something like BountySource or Patreon help this along? I can throw a little cash in the pot (or buy you a bottle of your favorite wine or beer) if that would help :-). Thank you for this project! |
ping. |
Luckily I am still alive. I've setup a reminder for tomorrow... |
@kapouer - Any thoughts on fixing this? As per my above message, I'm willing to contribute via Patreon, BountySource, beer etc. |
ping @kapouer we have marked 4.1.1 released in the meanwhile which is not compatible. |
On to it ! |
Somewhat depending on markedjs/marked#2629 to avoid using another command line options parser. |
Fixed in version 1.0.0 |
Unmodified, immediately crashes with:
Ok, so that internal name is Lexer now in marked. Will a simple rename work?
Now the crash is:
The text was updated successfully, but these errors were encountered: