You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since the latest commit appears to have been pushed in January 2019, and because a number of open issues / PR's (eg. #11, #13, #15, etc) appear to have been sitting around unanswered/unmerged for a while now; i'm wondering if this project is still active/maintained?
In #17 I compare with jekyll-commonmark and notice that it seems to be both more recently updated (June 2020), and due to a looser version pinning requirement, is able to use a more up to date version of the underlying commonmarker dependency (that this project also uses), which in turn allows it to use the most up to date version of libcmark-gfm (with likely associated performance, security, and feature improvements over the old version transitively pinned here)
In #17 (comment) I noticed an issue on the pages-gem repo claiming that it appears to use the default Jekyll Kramdown parser rather than this project, quoted below:
I also noticed github/pages-gem#699 which states that the pages-gem (which claims to version gem dependencies used by ghpages; updated in 2020, so seems active) appears to be using the default Kramdown parser, instead of this project, which casts further doubt in my mind as to what the 'correct' choice is.
Though looking at the pages-gem readme shows that we can also check the GH pages dependency versions online:
Since the latest commit appears to have been pushed in January 2019, and because a number of open issues / PR's (eg. #11, #13, #15, etc) appear to have been sitting around unanswered/unmerged for a while now; i'm wondering if this project is still active/maintained?
In #17 I compare with
jekyll-commonmark
and notice that it seems to be both more recently updated (June 2020), and due to a looser version pinning requirement, is able to use a more up to date version of the underlyingcommonmarker
dependency (that this project also uses), which in turn allows it to use the most up to date version oflibcmark-gfm
(with likely associated performance, security, and feature improvements over the old version transitively pinned here)In #17 (comment) I noticed an issue on the
pages-gem
repo claiming that it appears to use the default Jekyll Kramdown parser rather than this project, quoted below:Though looking at the
pages-gem
readme shows that we can also check the GH pages dependency versions online:Which shows a usage of
jekyll 3.8.7
andjekyll-commonmark-ghpages 0.1.6
, which appears to be the latest released version of this project.It would be great to get some insight from project maintainers about the status of this project.
The text was updated successfully, but these errors were encountered: