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
fromURL, loadBuffer, decodeStream missing #3101
Comments
@edemaine I have faced the same issue and revert to cheerio documentation. As per the documentation I have directly imported cheerio/lib/batteries to use fromUrl property but it seems to be missing. |
FWIW, I'm already using ESM via |
This hasn't been released yet — as the banner at the top of the website says:
I want to wrap up work on the website before issuing the release, but haven't been able to focus on that for a while. |
Thanks for confirming! I'm new to Cheerio so it was just a confusing on-boarding experience. (I just wrote my own fromURL for now.) The site looks great! Let me know if there's something you could use help with. I did have a docs wording suggestion for newcomers, so I'll go make a PR. |
Would love for this to become GA. It's such a great option for us |
Coming to this after 4 months, Please flag the docs accordingly: https://cheerio.js.org/docs/api#fromurl. Will raise a PR if required. |
I do not see any implementation of |
As they said, it hasn't been released yet |
It does appear that new loading documents have still not been released. I am upvoting this as it is confusing to work with a documentation of "future" when building tools for today. |
The documentation says that this should work:
or
However,
cheerio
does not appear to have afromURL
property, in the released NPM version 1.0.0-rc.12. Perhaps related to #2774? Similarly,decodeStream
whichfromURL
is built on,loadBuffer
,stringStream
all seem to be missing. I havecontains
,load
,html
,merge
,parseHTML
,root
,text
,xml
.As a first-time user to Cheerio, this was pretty confusing, as it seems like the easiest way to get started with the library.
The text was updated successfully, but these errors were encountered: