Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 21 days ago

React & Tailwind - Browser extensions manager UI solution

react, tailwind-css, vite
Anar•720
@anar-sol
A solution to the Browser extension manager UI 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?

Any comments are welcome =)

Built with

  • Flexbox
  • CSS Grid
  • React
  • Tailwindcss
  • Vite

Highlights

  • I extracted the core API to a separate module extensions.ts.

  • The extensions are sorted by name when displayed.

  • The list of extensions is loaded from localStorage (a hard coded list is used the first time):

function loadExtensions(storage?: Storage): Extension[] {
    const storedValue = storage?.getItem("extensions");

    if (storedValue) {
        try {
            return JSON.parse(storedValue);
        } catch (error: any) {
            console.error(error.message);
        }
    }

    return [..._extensions];
}
const [extensions, setExtensions] = useState(loadExtensions(window.localStorage));
  • The list of extensions is saved on localStorage:
function saveExtensions(extensions: Extension[], storage?: Storage) {
    try {
        storage?.setItem("extensions", JSON.stringify(extensions));
    } catch (error: any) {
        console.error(error.message);
    }
}
  • I added a button to reset the list to the initial value.

Useful resources

  • How to import SVG files as React components with Vite
  • Dark mode with tailwindcss
  • How to detect a user’s preferred color scheme in JavaScript

Continued development

With more time:

  • I would put more effort into the design.
  • Change the theme (dark / light mode) automatically when it is changed at the OS level.
  • Save the current theme on localStorage.
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 Anar'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.