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

Tip Calculator App with VITE + REACT

react, vite, bem
Jose Antonio Sánchez•470
@crimson3d
A solution to the Tip calculator app challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)
Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Timothé Bissonnette•480
    @Fable54321
    Posted 9 months ago

    I won't dig too deep in this one simply because, your react/javascript looks really good to me.

    I like the way you have handled the active tip selection. Only thing I could say is the reset button doesn't set the custom to either zero or it's initial "custom".

    Apart from this there is obviously some little designs mistakes, but I think you know how to fix these if needed.

    The responsiveness is fine, deifnitely functionnal, but I would recommend you to take a look at the clamp porperty while setting your width. I use it to set my preferred width in vw (Knowing the desktop width they use is 1440, I will take the width of the container and convert it in vw).

    With clamp you can also set a min value you don't want it to go lower then and a max value you don't want to go higher than. So let's say my preferred value is 60vw but I don't want it to go lower than 550px and not bigger than 1200xp. It will look like this: clamp(550px, 60vw, 1200px). For me this was a game changer, hope it can help you.

    Also consider slowly but surely looking for another way of structuring your css. I would suggest either going for modules.css, wich won't take you too long to understand and do a really good job or if you are willing to put just a little more time, maybe look at SASS/SCSS.

    Overall good job, keep 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

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