Christian Murphy

Hey @jayvdb! Thanks for opening a PR. This project isn't actively maintained anymore. https://github.com/wooorm/mdxjs-rs is its replacement. It would be nice if the projects could merge together again, see https://github.com/mdx-js/rust/issues/2,...

> still it would be useful to have the crate metadata accurate I agree, again see #2, there are currently no active maintainers with publish access to cargo. Without that,...

> that would make this project impossible to use in browsers though Could you expand on why this would break browsers? Would it make sense/be possible to include a plugin...

> arbitrary file or network access could result in security vulnerabilities I'm not sure I follow you you see this being different than the existing top level string based loader....

@danoszz friendly ping, is this still something you're interested in?

Another possible guide series. Using Unified with: * Rollup * WebPack * Angular CLI * Create React App * Vue CLI See https://github.com/unifiedjs/unified/issues/34 for context

There is also a [unified handbook](https://github.com/unifiedjs/handbook) now, is there any way these two efforts could be consolidated? /cc @johno

PRs enhancing and adding to the handbook are welcome!

`rehype` and `hast` have official typings for the HTML nodes. You can find them at https://www.npmjs.com/package/@types/hast The overall plugin can leverage the `Plugin` type, for example `import('unified').Plugin}` (for example: https://github.com/rehypejs/rehype-meta/blob/e5eae88704c300393641c71b9e3f59a780fc3ed7/lib/index.js#L145)...

@wooorm may be able to offer more context. From reviewing the description/spec https://talk.commonmark.org/t/generic-directives-plugins-syntax/444 I believe the intent is to be roughly compatible with html/custom element naming conventions https://html.spec.whatwg.org/multipage/custom-elements.html#valid-custom-element-name https://developer.mozilla.org/en-US/docs/Web/API/CustomElementRegistry/define#valid_custom_element_names which...