Matt Wang

Just to chime in @SamsungGalaxyPlayer - mermaid is disabled by default (if you consume the theme as a remote theme / gem), precisely for this reason. Are you copying the...

Okay, coming back to this now - I think I'm missing some context. @SamsungGalaxyPlayer, it sounds like for the site you're benchmarking against, you're *not* using mermaid, but you've copied...

Going to close this for now. Feel free to re-open if you have additional comments!

Looks like this was in limbo, so tried my hand at an implementation in #4893.

Thanks @jeddy3! (think I mangled the co-authored commit message, but I can add it when I merge)

I've been a bit behind on contributing - @ybiquitous did you want me to also edit `CHANGELOG`, or does the Changesets automation do that for us now?

Dropping Node 12 + switching to ESM in lockstep seems good to me as well! There is the knock-on effect of this helping out vscode-stylelint as well! What's the best...

> This is an opportunity to revisit ESM support. So, the most helpful thing to do is to continue the investigation in https://github.com/stylelint/stylelint/issues/5291 to determine whether using ESM is viable...

Looking at the changelog - > BREAKING: Require Node.js v14+ ([#497](https://github-redirect.dependabot.com/postcss/postcss-import/pull/497)) Sounds like this is related to #6311!

Thanks for the quick response Kevin! > The main place for possible upstream changes would be in _sass/custom/custom.scss where I have some stylistic overrides to provide different defaults for HTML...