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

Password generator app using React & Typescript

react, tailwind-css, vite, typescript
Duncan Chege•340
@duncan-chege
A solution to the Password generator app 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?
  • I'm proud of completing the project in the set timeframe I gave myself (5 days)
  • I'm happy I learnt how password generator apps operate
  • I'm happy I added a wavy background to the layout, to elevate the UI
  • For my first premium project, I'm happy that I got access to the design files
What challenges did you encounter, and how did you overcome them?
  • Generating the passwords in line with the checkboxes was a challenge but I solved it using chatGPT. Also, linking the password length to the slider was challenging but I solved it. It was all a learning process
Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Ilya Yudin•1,060
    @yudin7324
    Posted 6 months ago

    Your code is great, but I would suggest splitting it into smaller components. React is all about components, and breaking down the code would make it more maintainable and reusable.

    Here are a few reasons why: 1.Better Maintainability: Splitting the code into smaller components makes it easier to manage, especially as the app grows.

    2.Improved Reusability: By creating reusable components, you can avoid code duplication and make the code more flexible for future changes.

    3.Improved Readability: Smaller, well-defined components make the code easier to read and understand, helping both you and other developers work with it more efficiently.

    Good luck with the next challenge!🚀

    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

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