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

IP Address Tracker built with Next

tailwind-css, typescript, next
Jenny Eikens•250
@Jenny-Eikens
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?

This is the first project where I worked with APIs. I learned how to work with Next.js route handlers to make get requests. It took me some time to learn how to set up the function and understand how the Request object as a parameter, the URL API, and the Response API work in this context. I am proud of my final implementation.

I added a loading screen for the data returned by the geolocation API as well as the map so the screen wouldn't just be blank while those load.

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

I found the use of Next.js route handlers challenging at first because I had no experience working with them. The use of the Request object caused me a bit of confusion but thanks to some helpful YouTube videos and the Next docs, I got there in the end. I also found it a bit tricky to figure out how to conditionally set either an ip address or a domain as the search parameter.

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

Currently, when I open the page on a mobile device, the styling below causes the content to be cut off at the bottom because the space taken up by the address bar doesn't get taken into account (so the actual content doesn't span the full height of the viewport). Any ideas on how to fix this would be welcome!

<main className="flex min-h-screen flex-col justify-end">
Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Jenny Eikens'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

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.