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

Product-List-With-Cart made with TypeScript and Tailwindcss

react, tailwind-css, typescript, vite
Joe•20
@joefreeman8
A solution to the Product list with cart 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 really pleased to have completed my first TypeScript project, maybe a little overkill for a project as small as this, but I can see how it would be super useful on larger projects.

It was also fun to dive in to Tailwindcss. On other recent projects I had been using DaisyUI as a plugin for Tailwind, because it makes life easier and I quite enjoy the prebuilt styles it gives. So I used this project to get used to "vanilla" tailwind again.

If I were to do this again I would repeat it in TypeScript again, but would be a little more flexible with my css tools - I really wanted to get this pixel perfect, and while I think I didn't do too bad a job, I know it's not "perfect"!

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

Interfaces and ensuring all my datatypes are defined in each piece of state or function. That sure slowed me down. The other tricky bits were getting the css how I wanted it to be for the different devices.

I made the mistake of cracking on with a large screen and styled accordingly, it would have for sure been easier to start mobile and build from there - as then the generic sizes are all for mobile and the tailwind sizings won't miss!

This piece of code took me a while to figure, the key was remembering that I can pass "prevCart" within setCart, to get the latest data/info which is inside of setCart.

 function handleAddToCart(dessert: Dessert) {
    setCart(prevCart => {
      const existingItem = prevCart.find(item => item.name === dessert.name)
      if (existingItem) {
        return prevCart.map(item =>
          item.name === dessert.name ? { ...item, quantity: item.quantity + 1 } : item
        )
      } else {
        return [...prevCart, { ...dessert, quantity: 1 }]
      }
    })
  }
What specific areas of your project would you like help with?

As it's my first time TypeScript'ing then I'm open to any feedback regarding it.

It's currently in dire need of being refactored into components, so I'm well aware of this. Just want to get it submitted and online asap. Will work on refactoring in the coming days.

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Joe'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
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.