We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
We made html5ever and Floki work together through ex_html5ever thanks to @hansihe and the Rustler team! 👏
Using ex_html5ever can be very useful those who need a more accurate parsing of the HTML. It solves the issues #50 and #75, for example.
ex_html5ever
Since ex_html5ever relies on a Rust NIF, it requires the user to have Rust installed.
Also I ran some benchmarking that shows the ex_html5ever version is faster from the average to big HTML files. ⚡️
UPDATE: the html5ever Elixir NIF was named to "html5ever" on Hex.pm, and the repository is now https://github.com/hansihe/html5ever_elixir
The text was updated successfully, but these errors were encountered:
Closed by #90 .
It was released in version 0.14.0.
0.14.0
Thank you @hansihe and @aphillipo!
Sorry, something went wrong.
philss
No branches or pull requests
We made html5ever and Floki work together through ex_html5ever thanks to @hansihe and the Rustler team! 👏
Using
ex_html5ever
can be very useful those who need a more accurate parsing of the HTML. It solves the issues #50 and #75, for example.Since
ex_html5ever
relies on a Rust NIF, it requires the user to have Rust installed.Also I ran some benchmarking that shows the
ex_html5ever
version is faster from the average to big HTML files. ⚡️UPDATE: the html5ever Elixir NIF was named to "html5ever" on Hex.pm, and the repository is now https://github.com/hansihe/html5ever_elixir
The text was updated successfully, but these errors were encountered: