Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 4 months ago

QR code generator component for links

axios, sass/scss, vite, node
Arash Asghari•250
@AriArash44
A solution to the QR code component 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?

Positive aspects of this project:

  • I am glad to have used SCSS and PurgeCSS to generate optimized and reusable stylesheet code.
  • I successfully integrated an API to generate QR codes based on user input.
  • I learned how to deploy my project on Vercel and GitHub Pages.
  • I gained an understanding of how to secure API keys by making server-side requests.

What I would do differently in my next project:

  • First, I will start with the backend, ensuring that all endpoints are fully developed and tested using Postman.
  • Once the backend is stable and functional, I will proceed with the frontend implementation.
What challenges did you encounter, and how did you overcome them?

Challenges:

  • The deployment process was completely new to me.
  • The API provides images directly in SVG format, so rendering them using Base64 encoding techniques and related methods was a new learning experience.
  • At times, I updated the README markdown file directly on GitHub but forgot to pull the latest changes before committing locally. This led to merge conflicts, which were frustrating to resolve.

How I overcame the challenges:

  • I searched the internet and used AI chatbots (ChatGPT and Copilot) to help me through the process.
What specific areas of your project would you like help with?

I appreciate any suggestions regarding project structure and code improvements to enhance readability and ensure adherence to clean code principles.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Victor Lantigua•50
    @lantiguav
    Posted 4 months ago

    Works great. Good job.

  • DrMetr•300
    @DrMetr
    Posted 4 months ago

    Yo, this is impressive! 😲 You're cool, keep it up!

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

Oops! 😬

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

Log in with GitHub