Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted almost 3 years ago

Expenses chart component with Native JS

nunjucks, tailwind-css, fetch
Plinsinga•310
@codedforfree
A solution to the Expenses chart component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


So I have to say I'm childishly proud of something that's probably really easy for a lot of you out there. But my Javascript skills getting better every day. Because I use nunjucks for these projects, my normal route would be to just iterate over this data with a foreach loop, but knowing I need to challenge myself on Javascript I tried to use native javascript instead.

Not knowing where to start led me to a solution of @elaineleung and this was really helpful. I never heard of things like createRange or createContextualFragment but these were really helpful. Thanx @elaineleung!

One thing I did a bit differently is the way a render the bars. While @elaineleung is appending it to each bar,

<div id="barsEl" class="spending__bars bars">
            <div class="bars__day"></div>
            <div class="bars__day"></div>
            <div class="bars__day"></div>
            <div class="bars__day"></div>
            <div class="bars__day"></div>
            <div class="bars__day"></div>
            <div class="bars__day"></div>
          </div>

I appended each bar inside its main container.

<div data-chart class="flex justify-between mt-[52px] items-end"></div>

I'm not sure if this is totally not the way to go but I thought it was a nice personal touch to some 'stolen' ideas ;).

I hope you like it and please give me some feedback on how to improve.

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 Plinsinga'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.