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

Move scrapeHTML into its own package #161

Closed
malte-v opened this issue Jan 9, 2021 · 1 comment · Fixed by #163
Closed

Move scrapeHTML into its own package #161

malte-v opened this issue Jan 9, 2021 · 1 comment · Fixed by #163
Assignees

Comments

@malte-v
Copy link

malte-v commented Jan 9, 2021

I'd like to use your package from a React Native app, where the Node.js core modules are not available. scrape-it indirectly depends on tinyreq, which in turn uses Node's url module. I'm only using scrapeHTML, so all the networking stuff is not required. Could you move scrapeHTML into its own package, say "scrape-it-core", so people can use the offline functionalily independently? Thanks!

@IonicaBizau
Copy link
Owner

I was thinking of this too. Perhaps will wokr on this next days. Thanks for the idea! ✨

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

Successfully merging a pull request may close this issue.

2 participants