Tony Brix

This is because `strong` is an inline token and `heading` is a block token.

It is still possible to narrow with `const textToken = token as Token.Text`. If you have a better idea on how to fix it PRs are always welcome 😁👍

IMO that is actually better, because even though it is possible that token is not type Token.Text if the type === 'text' it is explicitly stated in the code that...

I do agree that we should limit the type string in Generic to any string that is not one of the main token types. If you can find a way...

I agree that token.type should identify the token. I just don't know how to do that in typescript when Token.Generic.type can be any string. Using `as Token.Text` just tells typescript...

> what's the problem? First thing I see is that the extension tokenizer can only return one of the current tokens. This is totally wrong and will break almost every...

rebase on the latest version of marked. I fixed a few types and removed `& { loose?: boolean, tokens?: Token[] }` from the Token type. It could work to extend...

All of those benefits seem possible without marked being the holder of this data object. For example the marked-gfm-heading-id extension provides a list of the headings for a table of...

I don't feel like our build times are a problem. They are only a couple seconds currently. I went with terser because the plugin is developed by rollup and more...

I've never used vite, but I'm all for learning new things. Are you talking about replacing our docs with vite?