Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 1 year ago

Responsive IP Address Tracker with Nuxt 3, Geoipify, and Nuxt3-Leaflet

nuxt, pinia, vue, tailwind-css
Muhamad Rizki Ismail•180
@rizkiismail9a
A solution to the IP Address Tracker challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


I have an issue while using fetching data built-in library in Nuxt. I ended up using axios since I can't put the data in the store with useFetch or $fetch. I have no idea what happened. I also use ipify to get my own/user IP Address, but after I deployed it in netlify, it always returns a random IP Address from nowhere. It was good when I was still in localhost:3000 I also have no idea what happened. Can anyone help me to solve the issue? Thank you

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • otr-web-study•300
    @otr-web-study
    Posted over 1 year ago

    Hi, Muhamad Rizki Ismail. Try to put data in the store using the useFetch's interceptor onResponse. Something like this:

    await useFetch(API_URL, {
      onResponse({ response }) {
        const data = response._data;
        // put your data in the store here
      },
    });
    

    As for getting the client's IP address, then you need to take into account the fact that the code from the server folder is always executed in the context of the server, i.e. in your case, this code is executed on the netlify.app server. To get the client's address, you can use the HTTP header - x-forwarded-for. For example, like this:

    export default defineEventHandler((event) => {
      const clientIP = event.node.req.headers['x-forwarded-for'];
      // fetch clientIP's information here
    });
    
    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