visit
started as an excuse to learn some new tech and challenge myself across the full stack. I knew I wanted to build a web scrapper with / and try out , a search-as-a-service platform.
I was probably browsing themes around the same time. Browsing the for themes can be painful. The site is optimized for browsing extensions so you rely on theme publishers adding screenshots to the readme.The search results aren’t super useful either. The name, thumbnail and number of installs of an extension are poor indicators of a theme’s quality. Browsing results one by one, hoping there’s screenshot, is a slow and frustrating experience.
I’m happy to announce that I’ve pushed some big updates to the site over the last few months that will help you discover some new awesome themes. Read on for details on some of the more notable updates or see them in action at .I originally used the component for displaying code previews but it uses under the hood — which is not what VSCode uses for it’s syntax highlighting.
This meant I had to translate VSCode themes to PrismJS themes and resulted in widely inaccurate previews (in addition to some pretty nasty code). After digging around the VSCode source, I found the package that’s responsible for outputting color tokens for a given theme, language and template. This library depends on native modules so I couldn’t simply add it to the front-end. The latest update now pre-renders each language preview for a theme before saving the result to Algolia.Syntax highlighting before and after Check out for more details on how this works.
Search results before and after
Extension page with theme rotator Check out for more details on the front-end rewrite.