Skip to content
  • Learning paths
  • Challenges
  • Solutions
  • Articles
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 1 year ago

React, Axios,Tailwind css, Vite, Github API, useState, import.meta.env

react, tailwind-css, accessibility
Ann Mukami•260
@Kiunga1
A solution to the GitHub user search app challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Unable to Fetch Data After Deployment

Hello everyone,

I hope you're doing well. I recently deployed my React Vite app, which was fetching data from the GitHub API during development without any issues. However, I've encountered a challenge after deployment – the app is no longer able to fetch data.

I would greatly appreciate your feedback and assistance in troubleshooting this issue. Here are some details:

  • The app uses Axios to make requests to the GitHub API.
  • I've set up a GitHub token using ``` import.meta.env.VITE_GITHUB_TOKEN````.
  • The app was working perfectly during development, but the data fetching issue surfaced after deployment.

If you have any insights or suggestions on what might be causing this problem, or if there are specific areas in my code that I should review, please let me know. Additionally, if you have encountered similar issues or have best practices for handling API requests in a production environment, I'd love to hear your thoughts.

Thank you in advance for your time and assistance!

Best regards, Ann.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Ann Mukami's solution.

Join our Discord community

Join thousands of Frontend Mentor community members taking the challenges, sharing resources, helping each other, and chatting about all things front-end!

Join our Discord
Frontend Mentor logo

Stay up to datewith new challenges, featured solutions, selected articles, and our latest news

Frontend Mentor

  • Unlock Pro
  • Contact us
  • FAQs
  • Become a partner

Explore

  • Learning paths
  • Challenges
  • Solutions
  • Articles

Community

  • Discord
  • Guidelines

For companies

  • Hire developers
  • Train developers
© Frontend Mentor 2019 - 2025
  • Terms
  • Cookie Policy
  • Privacy Policy
  • License

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

How does the accessibility report work?

When a solution is submitted, we use axe-core to run an automated audit of your code.

This picks out common accessibility issues like not using semantic HTML and not having proper heading hierarchies, among others.

This automated audit is fairly surface level, so we encourage to you review the project and code in more detail with accessibility best practices in mind.

How does the CSS report work?

When a solution is submitted, we use stylelint to run an automated check on the CSS code.

We've added some of our own linting rules based on recommended best practices. These rules are prefixed with frontend-mentor/ which you'll see at the top of each issue in the report.

The report will audit 1st-party linked stylesheets, and styles within <style> tags.

How does the HTML validation report work?

When a solution is submitted, we use html-validate to run an automated check on the HTML code.

The report picks out common HTML issues such as not using headings within section elements and incorrect nesting of elements, among others.

Note that the report can pick up “invalid” attributes, which some frameworks automatically add to the HTML. These attributes are crucial for how the frameworks function, although they’re technically not valid HTML. As such, some projects can show up with many HTML validation errors, which are benign and are a necessary part of the framework.