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

VITE, Bootstrap, SASS, API Leaflet , API IPify

bootstrap, fetch, node, sass/scss, vite
Paweł•240
@H4m4k
A solution to the IP Address Tracker challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Project has been completed and delivered with VITE package manager and a lot of satisfaction due to many struggles along the way.

Technologies:

  • VITE - server / bundler
  • Bootstrap
  • SASS
  • API - Leaflet and Ipify

Problems occured:

  1. API key security , environment variables , package manager?
  2. What is a package manager and how do i use it ? what is better Webpack or VITE?
  3. How do I use VITE and what are npm scripts?
  4. What is CORS and SOP?
  5. type="module" in script tag is the only way i know to use import and export in js modules , so why can't I use console to debug before coding Leaflet API functions for map control ? what is strict mode ?
  6. API and Fetch

Solutions :

  1. Using a package manager (VITE in his case) and development server ( backend ) allowed the use of .env files which are the base of keeping security of the environment variables
  2. and 3. Research outcome was in favour of VITE as the new and faster technology. I have spent hours with Vite documentation , Stack Overflow and Googling web to understand the concept of packing the assets into as few files as possible as well as why the hell do i need a backend . After that i spent even more hours learning how to configure a working development environment , what is npm and how to use it.
  3. Setting proxy in VITE was the solution, but that is the effect of a few hour research about Cross Origin Resource Sharing and Same Origin Policy
  4. It happens that when in strict mode there are no user global variables available and You need to be very precise with addressing your communication between JavaScript modules, preferably by communicating with functions (that worked for me). Created an completely clean website just for this purpose and debugging.
  5. API and fetch was very easy and proved to be of a little challenge. Challenge emerged when i had to use two API to get the data and coordinate JS modules communication and functions synchronization between each other.

Conclusion, demanding challenge that i am happy to have overcome with hours of reading , research and work. As a touch of my creativity I have added a opacity transition for the info panel in mobile to clear the users view. When it disappears just click or touch and it will show itself back.

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 Paweł'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 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.