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

product list with cart react javascript css html

react
Luis•270
@luisv79
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?

In this project, I was able to apply concepts such as the use of reusable components, Props for passing information, States with useState, Effects with useEffect, Events in React, and Bootstrap for the design.

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

The correct use of React properties gave me a lot of problems with connecting the components, but with persistence and searching the documentation I was able to resolve it.

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

Always good advice and guidance to improve and learn is always welcome.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Jay Khatri•4,230
    @khatri2002
    Posted 5 months ago

    Hi @luisv79!

    The developed solution looks great! However, it's very clear that the images are not getting loaded.

    Issue: Incorrect Image Path in data.json

    You're using relative paths like:

    {
      "image": "./src/assets/images/image-waffle-thumbnail.jpg"
    }
    

    This might work in the development environment, but it will break in production because of how React handles static assets when building the application.

    Solution: Move Images to the public Folder

    If you want to keep the images accessible via direct URLs, you should move them to the public folder.

    1. Move the images to the public folder:
    /public
        /images
            image-waffle-thumbnail.jpg
    
    1. Update data.json with the correct URL:
    {
      "image": "/images/image-waffle-thumbnail.jpg"
    }
    

    Why This Works

    • React does not process the public folder during build, meaning files stay available as-is.
    • Files in public are directly accessible via / paths like:
      https://your-app.com/images/image-waffle-thumbnail.jpg
      

    Hope that helps! Let me know if you need any additional help! Keep up the great work! 🚀

  • Masseh•260
    @Masseh2025
    Posted 6 months ago

    Congratulations for attempting this challenge. Some things I would say would be to start off small and make mini projects that emphasize some of the aspects in this projects such as implementing a counter. I would advise you to look at react context, and redux for state management. Anyways congratulations for attempting something hard.

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

Oops! 😬

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

Log in with GitHub