Skip to content
New issue

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

Version bump: Support cheerio 1.0.0-RC3 with parse5. #80

Closed
wants to merge 2 commits into from
Closed

Version bump: Support cheerio 1.0.0-RC3 with parse5. #80

wants to merge 2 commits into from

Conversation

AlynxZhou
Copy link

Cheerio 1.0.0-RC3 uses parse5 instead of htmlparser2 for HTML parsing, but parse5 decode all entities (include <, >) and does not support decodeEntities and normalizeWhitespace. This PR adds escaping function to support parse5 and updated cheerio dependence version.

Solves cheeriojs/cheerio#1198.

Needs a dependence version update for cheerio because this cannot keep compatibility with older cheerio (which uses htmlparse2 as HTML parser), older cheerio should use older dom-serializer.

@curbengh
Copy link

curbengh commented Aug 9, 2019

There is a diff conflict due to #76. Can you rebase?

@AlynxZhou
Copy link
Author

@curbengh I'd like to do after I read new code because other PRs has been merged since I write this PR, and hope maintainers can read cheeriojs/cheerio#1198 to understand what cause this problem, and they may have other opinions.

@AlynxZhou
Copy link
Author

I would like to make another PR and close this since I think this will make it easier for me to merge new code...

@AlynxZhou
Copy link
Author

Please refer to #85 for my new code, sorry for everyone comes here.

@AlynxZhou AlynxZhou closed this Aug 9, 2019
@curbengh
Copy link

That explains

npm ERR! Command failed: git checkout 91dcb1857a7a304ea83c7c68713bf6dacfc496d5
npm ERR! fatal: reference is not a tree: 91dcb1857a7a304ea83c7c68713bf6dacfc496d5

I'll update my package to refer to the new PR instead.

Thanks for the update.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants