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

REST Countries API (TypeScript, React, Context API, SWR, Playwright)

accessibility, emotion, fetch, react, typescript
Aman Singh Bhogal•1,010
@asbhogal
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


A refactored version of an initial challenge which pulls data about countries from around the world and lists their information, with an option to filter by region, search for a country, view more details about a country (dynamic routing) and a switch between light and dark mode. Created using TypeScript with React, styled using Material UI with skeleton loading states, SWR for client-side data fetching and Playwright for E2E and a11y testing.

Features

  • TypeScript for type safety
  • SWR for client-side data fetching from REST API endpoint
  • Dynamic routing for individual countries
  • Material UI for style and theming
  • Skeletons for UI component loading states
  • Playwright for E2E and a11y testing
  • Husky for running linting and a11y tests prior to git commit

Refactors

  • Full migration to TypeScript
  • Replaced useEffect and axios with SWR
  • Implemented skeleton loading for UI components on Dashboard
  • Improvements to accessibility and semantic markup on pages
  • Further organisation of dirs
  • E2E and a11y testing using Playwright (replaces Cypress)
  • Image fit changes (cover to contain)

Stacks

  • TypeScript
  • React
  • SWR
  • Material UI
  • ES Lint
  • Playwright
  • Husky
  • Vite
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 Aman Singh Bhogal'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 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.