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

CSS GRID, VITE BUNDLER, TYPESCRIPT, VANILLA JS, SASS, FETCH

accessibility, fetch, vite, sass/scss
Benjamin•130
@Benjoow
A solution to the Time tracking dashboard challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hello everyone!

I wanted to make this project only in javascript vanilla. It was not the easiest way but it allowed me to review the basics of creating elements in js.

I had some difficulties with the types while manipulating object data and I had to change my html and css structure because of a bad implementation of the absolute position.

Please feel free to give me some ideas to improve my code, it would be a pleasure especially on typescript.

Thank you.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Devmor•470
    @devmor-j
    Posted about 3 years ago

    Beautiful 🥰 I went through your code and I have to admit that all those packages scare me 😁. Some might say this is an overkill solution but in my opinion this sure could be an enterprise structure that provides scaling and online fetching in mind. Just being honest and hope this does not offend you my dear.

    One thing that I highly recommend is that in tsconfig file set your target to something like es2016 or es5. This will bring support to a broader range of browsers and almost all of them support es5 syntax:

    "compilerOptions": {
        // try 'ES5' or 'ES2016'
        "target": "ESNext",
    }
    

    Currently ESNext is not safe and causes ambiguity (imagine 2025 in which esnext means 2026). I personally would only use esnext just for development and not production or final bundle.

    Overall I enjoyed your well-organized repo and names make sense, Have fun 😀

    Marked as helpful

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 1st-party linked stylesheets, and styles within <style> tags.

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.

Oops! 😬

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

Log in with GitHub