Titus

Thank you! > Let’s use an patch load-plugin to use an AggregateError and a dedicated error message as per Which patch **exactly**? > From just the error message I can...

Coming back to this, I do think an `AggregateError` is meant for multiple errors, and it is better than `throw lastError`. However, I do think it is a **major version**:...

I don’t think I can do anything about that though?

I don't maintain or use this package?

Can you make this idea practical with a realistic input/actual/expected example?

Right, right. Yeah, I think this makes sense. Want to work on a PR?

Done in [`7.1.0`](https://github.com/syntax-tree/mdast-util-toc/releases/tag/7.1.0). Thank you!

Inlining what I believe Sebastian links to: Users can support ~the unreleased version of~ React 19’s types by defining the `JSX` namespace that they remove: ```ts import type {JSX as...

I believe this no longer appears; the code in the OP is no longer there: ``` export function MDXProvider(properties: Readonly): React.ReactElement; ``` Last local use of `JSX` was in the...

Hey! Did this work for you locally? Are you still working on making CI green?