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

REST countries using React & Tailwind-CSS, built with Vite

react, tailwind-css, vite, react-router
nikoProg•120
@nikoProg
A solution to the REST Countries API with color theme switcher challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


This was the toughest challenge so far and it helped me understand React a bit better. There's still a lot to learn about routing and loading items synchronously! Often, I was getting an error "can't do function on undefined", because my JSX wanted to load before the items were downloaded from the API, so it would load NULL or undefined! I made a few workarounds for it, but I believe it can be done much better.

This was also my first project in Tailwind-CSS. It's quite handy and really quick to figure out. Their documentation is great.

One design choice I gave up on was simply downloading all countries once and then just filtering them based on different properties. I did not do this because https://restcountries.com already gives us methods for filtering. Was this a good choice?

A small thing people may or may not notice is that links to border countries are actually country codes and those always return 1 object, not an array. I was getting burned out, so I did not finish making a better solution.

What are the best ways to compartmentalize a React project? I am not sure! How many folders should I have and for what purposes?

All constructive feedback is appreciated.

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