Closed hyrious closed 10 months ago
Maybe integrating lightningcss, or making a fork of the css module to add supports (it is not updated for 2 years).
I think we should switch. CSS doesn't stop evolving, so it doesn't make sense to continue maintenance of an abandoned package.
This PR did various changes to make it work with the latest styles from GitHub.
light
section here: https://cdn.jsdelivr.net/npm/github-markdown-css@5.4.0/github-markdown.cssWhich means it now adds classes like
markdown-alert-note
markdown-alert-title
octicon-info
mr-2
to the ALLOW_CLASS set.@container
to make it able to parse GitHub CSS again.To read the output diff:
Next steps:
As I mentioned in #27, GitHub will use newer CSS syntaxes from now on -- they are using
@container
, maybe the next is@layer
or even CSS nestings. We need not a workaround but a solution to parse these new CSS syntaxes. Maybe integrating lightningcss, or making a fork of thecss
module to add supports (it is not updated for 2 years).