Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted about 1 year ago

Tip calculator app with TypeScript, TailWind, and Vitest

tailwind-css, typescript, vitest
P
Thomas Dimnet•250
@tdimnet
A solution to the Tip calculator 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?

Hi Folks 👋,

Thank you for reading this.

For this project, I wanted to do something more than just working with plain CSS and vanilla JavaScript.

This project uses:

  • TypeScript - To be honest, there is not too much of it in the project - it's just a single-page app after all - but it was fun and I really enjoyed using it.
  • Tailwind - I was waiting for the right first project on Frontend Mentor to use Tailwind. I decided this one was a good one :).
  • Vitest - One of my objectives was to start adding unit tests to my Frontend Mentor projects. I have only one test case. I could have added functional tests, but I thought it was a bit overwhelming.
  • GitHub Actions - The project is automatically deployed on GitHub with a build phase thanks to GitHub Actions. It's not perfect yet (I have to do a little tweaking for the index.html file).

I am going to take some time to understand more about Vite, especially Vite config for projects without a front-end framework.

What challenges did you encounter, and how did you overcome them?

Not too many: I wished I had more time to work on it, but these last few weeks have been quite busy.

Decoupling the different parts of the TypeScript/JavaScript was fun, and I had to think a bit before implementing it. I rewrote some parts of the code in order not to use DOM objects and only primitives.

What specific areas of your project would you like help with?

Let me know if you find incorrect things in the code or bugs. I think having a bit a feedback on the TypeScript code would be great.

Have a nice day,

Tom.

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 Thomas Dimnet'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.