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

using sveltekit with static site + test

svelte, vitest
P
JConan•90
@JConan
A solution to the Tic Tac Toe 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 successfully wrote tests in the TDD style, which have been invaluable during redesigns. Next time, I would aim to iterate faster on the test-design cycle to further enhance the process.

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

When adding AI to the system, the reactivity code didn't behave as expected. I identified the issue and corrected it, ensuring functionality, although the solution might not be the most optimal.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Joel Eguiza•350
    @joeleg96
    Posted 15 days ago

    Hey JConan,

    Overall good job on your solution, it looks very clean, and works very well. There are a few small details that you could fix though:

    1. I don't think you're using the correct font in the starting menu.

    2. I noticed that when you start a new round in both vs cpu and PVP X no longer goes first.

    3. I think it might be helpful to apply a delay to the CPU's turn rather than it going automatically, but this might just be a personal preference.

    This is just me nit picking for constructive criticism though. Great job on a great solution, and good luck on your coding journey!

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