Joe Pea

I think @jhildenbiddle is asking if we should even keep the cli or not, regardless where it is located. Agreed, a static server feature isn't really a high importance feature,...

> We could provide a tool on our website that is similar to the one offered on sites like [prismjs.com](https://prismjs.com/download.html#themes=prism&languages=markup+css+clike+javascript). That would be a big project that I won't have...

We could keep it in a separate repo, but then perhaps we should add a test that clones it (possibly as a git submodule), and verifies it works, with each...

Hi, can you provide a sample of the problem? For example markdown, links to site, etc. There is not enough information here to understand what you'd like to do.

Updated the title to reflect moving stuff into `dist/`

Hi @gigaga, if you make a pull request with the change we can evaluate it. I think it would be nice to be able to hook into any markdown rendering...

Not necessary to fix, the code works as-is. Looks like GitHub doing type checking. We can fix type errors as we go along. Later we can make type definitions for...

Let's chat about the concept, let me know what you think of this path. In the [last commit](https://github.com/docsifyjs/docsify/pull/2392/commits/1a352afa205342698aee91c3fc07a42c2f01a13a) I marked `$docsify` as "deprecated", and added `console.warn` messages. I also exposed...

The `console.warn` deprecation messages cause some playwright `expect(consoleMsg).toBeUndefined()` tests to fail, but that's easy to fix (should we even be testing that?). The code otherwise still works (back compat).

Hey guys, no offense taken at all! I usually propose ideas in the form of code changes. This could be a prototype to help discuss how type checking (without writing...