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

Product List Cart with Svelte 5, TypeScript and UnoCSS

svelte, typescript
Shawn Lee•580
@OGShawnLee
A solution to the Product list with cart 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?

Hello everybody. It's been a long time since I uploaded anything here. I am now studying Software Engineering and we haven't done any web development yet, only programming with C++ —real good for creating your own programming language— and Java —this one sucks big time—. I am a sophomore chilling.

I am pretty proud of how I handled the state management. I didn't need any crazy libraries like in React, instead I built Vue inside Svelte —Svelte 5 magic baby—. Also the animations are built-in. Svelte simply has everything you need.

I also used Bits-UI for the Dialog, a very cool headless (focus on sytling rather than scripting) library. You guys should check it out if you plan on doing any Svelte.

If anybody wants to collaborate on anything reach me out. I can probably help.

Have a nice day. I love you all.

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

Setting up UnoCSS. It's been like 2 months since I did web development with a fullstack proyect that didn't go anywhere —sighs—, and I got a 2 month burnout period —i am back baby—. I had no idea if the process of setting up UnoCSS is the same as it was.

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

I would like some help with semantic HTML and accessibility. Those are often the most overlooked aspects of web development. I often get kinda lazy with those things and leave it for a future feature update.

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 Shawn Lee'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 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.