Titus
Titus
You can see that our packages for [react](https://mdxjs.com/packages/react/#types), [preact](https://mdxjs.com/packages/preact/#types), and [vue](https://mdxjs.com/packages/vue/#types), each have the exact same types section. Depending on what wording you think of for react, I don’t think...
> (should pass when my code change is included, should fail with unexpected token ; when my code change is not included). 🤔🤔🤔 It still all just works for me...
> double-parsing is definitely less-than-ideal. I'd like to improve the situation with twoslash, but that is a big project and for now I just wanted to get this bugfix through....
Sweet! The answer is: ``yes, `element` is valid in a MDX hast tree``! Hmm, I still have can’t reproduce an error with a test like that: ```js renderToStaticMarkup( React.createElement( await...
Friendly ping! :)
Thanks everyone, particularly @calebeby and @bholmesdev, the reduced case helped a lot. I reduced it some more, uncovered the underlying problem, which I also fixed. And kept this length check...
Released in [`2.1.5`](https://github.com/mdx-js/mdx/releases/tag/2.1.5)!
But how far should this be taken? Such as, we could also hash content, e.g., you could generate ids based on the first 3 and last 3 words or so?...
Uhh that pinning is performative? Some tool is going to change them on every release right, and I don’t believe we’re vetting these actions for backdoors then? So it doesn’t...
- to reiterate, this repo uses dependabot to automatically update dependencies, if this scenario you show occurs, dependabot will pull that in: - https://github.com/inikulin/parse5/blob/master/.github/dependabot.yml - https://github.com/inikulin/parse5/blob/master/.github/workflows/dependabot-automerge.yml - there is nothing...