Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 2 years ago

IP Address Tracker with React and Vite

axios, react, vite
Olalekan Ben•80
@Olalekan-Adeyeye
A solution to the IP Address Tracker challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


It was really challenging and at the same time fulfilling. Uhm, some of the challenges I faced while coding are:

  1. Geolocation-db.com API (used to get user IP) returning crazy IP at times.
  2. React-leaflet map failing to work due to problem with CSS height property(took me a long time and a lot of googling to figure out).
  3. React-leaflet marker image not showing and at times pointing to wrong position (I did try my best to fix it with answers found on stackoverflow).
  4. fetch API returns CORS error most times (Axios fixed it but I don't know why axios would work and fetch wouldn't).
  5. Package.json showing error with no fault (a quick stroll through stackoverflow fixed it - Restart VSCode. Voila!).
  6. Images on the page not showing on production build and deployment to Netlify server (Happens that I was the one making the mistake all along - I spent all evening on this).

Well, I have a ton of things to write but that's all for now.

I will really like your suggestions on ways I can improve the code for faster and better performance

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Luiz Júnior•110
    @LuizAPJunior
    Posted over 2 years ago

    Hi! I looked a little bit into your code, here a couple of suggestions to improve your app:

    -I tried to search for a domain but I received an error message, it seems like you used the ipAddress parameter on Ipify's URL so I would recommend it to change ipAddress to domain so you can search for either ip adress or domain(just like in DNS) using the domain parameter.

    -You don't need to use geolocation-db to get the ip of the current user, in Ipify if you don't specify the ipAddress and domain parameters in URL the request will return the current user's IP (e.g. if you request https://geo.ipify.org/api/v2/country,city?apiKey=${API_KEY} will return your own IP ).

    -In case the maker still pointing to the wrong position, search for the useMap() hook from react-leaflet and the property setView(keep in mind that you can only call a hook in react components and at the top level).

    I hope that helps, best of luck!

    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 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.

Oops! 😬

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

Log in with GitHub