Cheerio: Please do not tag release candidate as latest

Created on 14 Dec 2018  路  4Comments  路  Source: cheeriojs/cheerio

1.0.0-rc.2 has bugs and should not be tagged as latest. Please tag it as next, and tag 0.22.0 as latest.

This issue is in response to #1260

Most helpful comment

I agree. Only stable releases should be tagged as latest. This tiny detail was breaking our new project when installing latest from npm.

All 4 comments

I agree. Only stable releases should be tagged as latest. This tiny detail was breaking our new project when installing latest from npm.

Hey folks,

Apologies for the issues during this transition period. Parse5 will solve a lot of outstanding bugs since it behaves more like the browser, but it is a breaking change for sure.

We're going to continue to support htmlparser2 because there are lots of cases where the browser/Parse5's "tree correction" is not what you want or expect. If you prefer to use htmlparser2's parser you can do:

const dom = htmlparser2.parseDOM(file.contents, options)
const $ = cheerio.load(dom)

Can anyone help with how to configure Enzyme to accept the htmlparser2: true option?

@astrotim I opened an issue with enzyme about this as it seemed noone had yet: https://github.com/airbnb/enzyme/issues/2299

Was this page helpful?
0 / 5 - 0 ratings

Related issues

robogeek picture robogeek  路  4Comments

trevorfrese picture trevorfrese  路  4Comments

miguelmota picture miguelmota  路  3Comments

misner picture misner  路  3Comments

dandv picture dandv  路  5Comments