Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 11 months ago

IP-Address-Tracker-scss-axios-v2

react, sass/scss, vite, axios
Teodor Jenkler•4,040
@TedJenkler
A solution to the IP Address Tracker challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


What are you most proud of, and what would you do differently next time?

I’m proud of successfully integrating the API and Leaflet maps, even though this was a practice project with limited time investment and improving on my old project.

I’d focus on refining the styling and addressing design inconsistencies. For now, I’ll leave it as is and start a new project this weekend.

What challenges did you encounter, and how did you overcome them?

Challenges Encountered:

One major challenge was handling environment variables for the hidden API key during deployment. Configuring them for different environments was difficult, especially with GitHub Pages.

How I Overcame Them:

I resolved this issue by switching to Netlify, which made managing environment variables much easier and will try learning gh pages more later.

What specific areas of your project would you like help with?

SCSS Feedback: I'd appreciate feedback on my SCSS code, particularly on how to improve styling consistency and maintainability.

Custom Hooks/Fetch Logic: Guidance on optimizing custom hooks and fetch logic would be valuable. Any tips on improving the efficiency or structure of these would be great.

Environment Variables on GitHub Pages: I encountered difficulties with setting up environment variables on GitHub Pages. An example or explanation on how to manage environment variables in this context would be extremely helpful.

(I know the responsiveness is lacking and some details are missing, but given the scope of this project, I feel it’s sufficient for now.)

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    MikDra1•7,450
    @MikDra1
    Posted 10 months ago

    Hi,

    I see that your app overflows a little bit. To repair it I encourage you to use this technique

    .container {
    overflow-x: hidden;
    }
    

    Hope you found this comment helpful 💗💗💗

    Good job and keep going 😁😊😉

    Marked as helpful
  • Solomon Obanijesu Philip•1,200
    @Hackerbot24
    Posted 11 months ago

    @TedJenkler Nice Job and it's Magnificent but I notice that your footer was not available and the icon was not there also

    Marked as helpful

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 all CSS, SCSS and Less files in your repository.

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.

How does the JavaScript validation report work?

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

The report picks out common JavaScript issues such as not using semicolons and using var instead of let or const, among others.

The report will audit all JS and JSX files in your repository. We currently do not support Typescript or other frontend frameworks.

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