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

Rock, Paper, Scissors using Vite, Tailwind, Vue 3 and Pinia

tailwind-css, vite, vue, pinia
Warren•650
@warrenlee
A solution to the Rock, Paper, Scissors game challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Another very interesting challenge and fully enjoyed coding this. I used Vue 3 and Pinia to state manage the game like keeping track of the score, the counter the player chose and managing which screen should be shown.

I do prefer to use Vue when there's transition and animation involved between components as I think Vue handles this well. The layout is fully responsive which turned out quite well.

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • Teresczuk Gabriel•220
    @gabrielteresczuk
    Posted almost 3 years ago

    Nice desing man!. I really loved the animation between the interactions. I saw just a little visual problem, with the backgrand color, when you put the height: 100vh, the background breaks any content after 100vh, and the backgraund repeat the gradient. -tested in 375px after win/lose the hand.

    Muy buen diseño!, me encantaron las animaciones entre las interacciones. Solo encontre un pequeño problema visual, con el background color, cuando pones height:100vh, the fondo se rompe al pasar ese 100vh y repite el mismo radial gradient. -tested in 375px despues de ganar/perder la mano.

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