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

Expenses Chart Component - Vite + React

react, vite, chart-js
Keith•190
@KeithEsc
A solution to the Expenses chart component 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?

Worked directly with React for the first time and used Main.tsx and App.tsx files to create my page. This was overkill for this solution but I wanted to get my eyes on a React project layout.

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

Ran into an issue with how my chart (made with Chart.js) was being styled within the bottom flexbox of the component. Ended up having the mess with some margins and sizes that I would have rather not needed to change to get desired solution look.

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

I am aware the font sizes, margins, and paddings are not exact and am ok with that. Feel free to give me some input on any errors you notice or changes that you would make to improve the code.

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

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

    Hi! The developed solution looks really impressive! You've utilized the Chart.js library to render the bar chart, and it looks awesome!

    However, it’s worth noting that the primary purpose of this challenge was to create the bar chart from scratch, as specified in the challenge description. While using libraries like Chart.js is an excellent practice for real-world applications, building a custom solution here will demonstrate your ability to handle such tasks independently and showcase your core skills in DOM manipulation, CSS, and JavaScript/React.

    I would highly recommend building a custom bar chart by dynamically creating the bars and scaling them based on the data provided. This way, you’ll gain deeper insights into how visualizations are built from the ground up!

    Amazing work so far! Keep going, and happy coding! 🚀

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.

Oops! 😬

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

Log in with GitHub