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

Issue: Data Not Fetched Correctly by GitHub Scraper #159

Open
JoshiUtsav opened this issue Nov 7, 2024 · 6 comments
Open

Issue: Data Not Fetched Correctly by GitHub Scraper #159

JoshiUtsav opened this issue Nov 7, 2024 · 6 comments

Comments

@JoshiUtsav
Copy link

JoshiUtsav commented Nov 7, 2024

Problem Description

When using the GitHub scraper package in my portfolio project, I noticed discrepancies in the fetched data compared to my actual GitHub profile. Specifically:

  • Repository Count: The package reports 40 repositories, while my GitHub profile lists 42.
  • Star Count: The package displays 22 stars, though my profile shows 2 stars.

This results in inaccurate data representation, which can affect applications relying on precise GitHub metrics.

Screenshot 2024-11-07 135346

Screenshot 2024-11-07 135634

@JoshiUtsav
Copy link
Author

@nelsonic.

@nelsonic
Copy link
Owner

nelsonic commented Nov 7, 2024

@JoshiUtsav thanks for informing us. This is GitHub (MSFT) changing their UI to break scraping. 😕
We can update the selector and it will work again. 🧑‍💻 ⏳

@JoshiUtsav
Copy link
Author

Why is there a CORS issue in production?

@nelsonic
Copy link
Owner

Are you attempting use this client-side?
We have only used it via Node/Deno and it works fine server-side.

@JoshiUtsav
Copy link
Author

Using this in the Next.js app.

@nelsonic
Copy link
Owner

Next.js should be able to run it all server-side. Where have you deployed it to? 🤷‍♂️

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

No branches or pull requests

2 participants