John Hildenbiddle

One option is to lock your JSDom version to [23.2.0](https://github.com/jsdom/jsdom/blob/main/Changelog.md#2320). This version uses a different selector engine which offers support for additional selectors like `:has()`. From the [changelog](https://github.com/jsdom/jsdom/blob/main/Changelog.md): > ##...

@juliangruber -- > All of my client side projects are transpiled, none of my server side projects are Yep. Same for me. Transpiling to ES5 for node isn't (usually) the...

> You can transpile ES6 code to ES5 code for browsers, so import isn't a deal breaker 🤔 Yep. I just propose that *you* (the library author) should do the...

I think discussions like this are most productive when we focus on problems that need to be solved. Perhaps I'm missing something, but so far I haven't read an "issue"...

To clarify, The “sass” package on npm *is* Dart Sass. Dart Sass compiles to pure JavaScript, so it is a drop-in replacement for node-sass (with some api differences and a...

We use two npm packages: 1) sass and 2) postcss (+ plugins). Sass will process `.scss` files and output `.css` files, then PostCSS will process the Sass-generated `.css` files and...

> What about postcss-env? [postcss-env](https://preset-env.cssdb.org/) is an interesting project. It can replace a preprocessor like Sass but only if the following are true: 1. Maintainer do not require or expect...

This issue has been addressed by PR #2469. The changes will be available when Docsify v5 is released.

Making sure I understand the issue: The goal is to avoid `` tags from being rendered as text when viewed outside of docsify, correct? For example, in [Typora](https://typora.io), the following...

I don’t understand. I thought the goal of this issue is to allow JavaScript to be added to markdown *and executed* by docsify while being completely ignored (i.e. not rendered,...