muji
muji
This issue represents the existing discussions on updating the AST to support a Commonmark compliant renderer. Related forum discussions: http://talk.commonmark.org/t/issues-to-resolve-before-1-0-release/1287 http://talk.commonmark.org/t/customizable-renderer-output-in-commonmark-js/1146/12 Originally discussed in #6.
For `lastLineBlank`, `htmlBlockType` and a `data` property which allows AST consumers to associate arbitrary data with an AST node.
Add support for the _htmlBlockType property on inline HTML elements; this allows AST consumers to be able to know ahead of time the type for inline HTML elements which is...
I am now serializing and deserializing the AST with a 1:1 exact match such that it could be converted to a JSON document and back to an AST tree. The...
Updating to use the recent changes we discussed I got bitten by the fact that I was using magic strings for comparing against `Node.type`, I suggest that `Node` expose constants...
This is derived from the [earlier PR](https://github.com/seanmonstar/reqwest/pull/1372) to add support for the `bytes_stream()` function for wasm32 but can be cleanly merged with current HEAD. The only difference is that it...
Hi @RustMania, I would like to try to upgrade the dependencies so we can support the `wasm32` target (see #31); I have already done this for `multi-party-ecdsa` with support from...
It would be very useful if `threshold-signatures` could support the `wasm32-unknown-unknown` target so we can use this library in the browser. Is there a roadmap for WASM compatbility? Is this...
Hi @miquels, I just tried this out in my project using `warp-compat` and it's working great, thanks :+1: I took a quick look around the code and was wondering whether...
See the [node exports documentation](https://nodejs.org/dist/latest-v16.x/docs/api/packages.html#packages_package_entry_points). The interesting thing about implementing this is that it *excludes access* to nested imports for files that are not explicitly mapped as exported by the...