-
Notifications
You must be signed in to change notification settings - Fork 7
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
Getting empty results #14
Comments
@qais-aboujaoude I think some changes were recently made to the pitchfork site and the DOM selectors were updated. however, the newest version of this package v0.0.16 on npm should work. If so, let me know and I can close this issue. |
Updated to v0.0.16. Now it works fine, both the API and the CLI. Thanks a lot. Funny thing. Today I decided to make my own pitchfork module. First time I do an NPM package and it's not working 😛 Again, thanks for the quick fix. |
😄 This particular fix actually came from a PR: #13 They've made a lot of subtle changes to the pitchfork website the past year or two, so it's been tough to keep up with all of them. Anyway, good luck with your pitchfork module and send me a link whenever you publish to npm. |
Whether I'm using the CLI or the API I'm not getting any results.
Last year things were working perfectly. Last time I tested it around January it was also working.
This seems to be a recent change.
If I log the search object here is the outcome:
The text was updated successfully, but these errors were encountered: