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

Simple QR Scan Component made with React and Chakra-UI

react, chakra-ui
Kawika Miller•90
@KMArtwork
A solution to the QR code component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


  • Do you think it was a good idea to use React + Chakra-UI instead of just creating everything from scratch?
  • Is there anything that doesn't make sense?
Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Aman Singh Bhogal•1,010
    @asbhogal
    Posted almost 2 years ago

    Hi Kawika,

    This is a good attempt, well done! While it's good to get exposure to libraries like React and Chakra UI, starting off its best to get a strong understanding of the fundamentals first, as frameworks and libraries are primarily built upon this. It allows you to then go into any particular direction without having a dependency on one particular tool. You'll likely also be tested on fundamentals in interviews too. Once you work your way up to the more advanced projects, libraries like React work great as they involve state management when handling data, and you'll also get more out of using UI Component libraries like Chakra UI. These junior and newbie challenges are designed to test and build your confidence with using pure HTML, CSS and JS. Using dependencies with this is also quite an over-engineered approach.

    Also, avoid using Create React App for client-side projects as Meta have stopped supporting it. Use Vite instead (they also support vanilla/pure HTML, CSS and JS environments too.)

    Hope this helps.

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

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub