Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 29 days ago

Memory game using vanilla-js

jss, van-js, vite, web-components, pure-css
P
K Akash Rao•150
@kakashrao
A solution to the Memory game 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 tried to make it entirely with vanilla JS, HTML and CSS without any framework or library to see the challenges that these frameworks and libraries solve with their approaches. I used Vite for building the application and deployed the build to firebase.

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

I can see how easy it became to build an application with frameworks and libraries like Angular, React, etc. The data management, view updates and maintaining code all become so easy with these technologies. But at the same time, the core idea remains the same, and that is JavaScript. I faced some challenges, mostly with long lines of code, but that was also mostly solved with Vite. Also handling of events, with vite one problem is that we need to module script when using it in html, and we cannot use direct onclick event with these scripts. But somehow I managed to solve that as well.

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

I want to know how do other people manages the challenges that I have faced, like long lines of code, using module scripts while dealing with click events, etc.

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

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