@jonathantneal Hi, Thank you for your interest, it is very important for us and we welcome any suggestions and are ready for action.

I’d love to see these features make their way into an existing library. I’m working on writing the most common Webpack, Express, Grunt, and Gulp bindings, as well as CLI tooling and a handful of common plugins necessary to make it worthwhile.

How would you be more comfortable to do this? and how can we help you?

If you are interested; could you let me know how I could help wire up PRs, or which features you might take issue with?

Upcoming planned work on the expansion of the api and the core can be found here.

👋 LGTM

not bad to see:

• tests
• default plugin example
• pref benchmark

support: Multiple matchers and Directives

support in Parcel

Oh this is wonderful; thanks for the warm response. I’ll get to work on performance benchmarks, as well as a default plugin example along with some real-world plugins.

I’ve been running all of my tests out of https://github.com/jonathantneal/posthtml/blob/master/.tape.mjs, but I also think it would be better to write tests alongside the code itself, like Result.test.js.

Thanks for sharing the milestones. It looks like my changes thus far could help with #221, #242, and #243.

I’m not sure of the request in #233 , but maybe it will be helpful to have what I’ve written for traversing and modifying attributes, as well as the support for duplicate attributes and attribute ordering (also useful for linting). As I said in my last post, I also want to add token list support so you can do things like element.attributes.get('class').add('intro') or element.attributes.get('aria-describedby') add('foo-help-text').

Here are some initial testing results:

Reshape:
  8378 operations per second
     5 cycles performed
  5.87 seconds elapsed

PostHTML (my fork):
 14019 operations per second
     4 cycles performed
 6.013 seconds elapsed

PostHTML (official):
126622 operations per second
     4 cycles performed
 5.957 seconds elapsed

I am using parse5 and I may be using the sax variation, while this project uses htmlparser2, which has the following stats:

gumbo-parser   : 34.9208 ms/file ± 21.4238
html-parser    : 24.8224 ms/file ± 15.8703
html5          : 419.597 ms/file ± 264.265
htmlparser     : 60.0722 ms/file ± 384.844
htmlparser2-dom: 12.0749 ms/file ± 6.49474
htmlparser2    : 7.49130 ms/file ± 5.74368
hubbub         : 30.4980 ms/file ± 16.4682
libxmljs       : 14.1338 ms/file ± 18.6541
parse5         : 22.0439 ms/file ± 15.3743
sax            : 49.6513 ms/file ± 26.6032

I will see if I too can switch to htmlparser2, as I can no longer remember why I chose parse5 to begin with. I think it was because I was pulling in ideas from reshape.