You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In general, I'm not super sure about the name of this option because in 0.22.0, decodeEntities actually prevents encoding the characters to HTML entities in the first place while no "encodeEntities" option exists. Since we're relying on this behavior, I had to downgrade to 0.22.0 for now.
Other dependents of cheerio also have this problem now, e.g. https://github.com/jonkemp/inline-css in version 4.0.0 is using the rc-* version of cheerio, which causes the same problem there. As described in #1261 tagging an rc as latest is probably the problem here.
The text was updated successfully, but these errors were encountered:
When using the latest-tagged version of cheerio on npm (1.0.0-rc12), decodeEntities apparently does not do what it was doing before.
Example:
With > 0.22.0 (1.0.0-rc*):
While with 0.22.0:
In general, I'm not super sure about the name of this option because in 0.22.0, decodeEntities actually prevents encoding the characters to HTML entities in the first place while no "encodeEntities" option exists. Since we're relying on this behavior, I had to downgrade to 0.22.0 for now.
Other dependents of cheerio also have this problem now, e.g. https://github.com/jonkemp/inline-css in version 4.0.0 is using the rc-* version of cheerio, which causes the same problem there. As described in #1261 tagging an rc as latest is probably the problem here.
The text was updated successfully, but these errors were encountered: