-
-
Notifications
You must be signed in to change notification settings - Fork 23.8k
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
cannot read properties of undefined (reading 'user') #2388
Comments
Before: Now please close this issue. The author has changed the URL of API. |
fix: Source URLhttps://github-readme-stats.vercel.app/api? change to https://github-readme-stats-git-masterrstaa-rickstaa.vercel.app/api? |
According to the instructions in anuraghazra/github-readme-stats#2388
Clearly not considering the readme was not changed to this url, the url has nothing to do with anuraghazra, his own profile hasn't been changed to reflect it and the fact a random url change like this would break everyone's profiles. That is just a self-hosted instance that is now being bombarded from everyone spreading it. |
fix an issue via anuraghazra/github-readme-stats#2388
I replace URL and its worked for me as well!
|
Thank you very much. |
See this issue anuraghazra/github-readme-stats#2388
fix the bug: Cannot read properties of undefined (reading 'user') See: anuraghazra/github-readme-stats#2388
The issue has been fixed in #2400, for more info see #2380 (comment) you may revert back to the original URL since rick's vercel account might not be able to handle millions of requests |
This reverts commit e3f4d8b.
The URLs were changed by the author and therefore it stopped working. See GitHub issue - anuraghazra/github-readme-stats#2388.
Describe the bug
Cannot read properties of undefined (reading 'user')
Expected behaviour
Cannot read properties of undefined (reading 'user')
Screenshots / Live demo link
Additional context
Something went wrong! file an issue at https://tiny.one/readme-stats
Cannot read properties of undefined (reading 'user')
The text was updated successfully, but these errors were encountered: