Browser Extensions Manager

What are you most proud of, and what would you do differently next time?

This was my first project in some time and I am happy that I have remembered a lot. The implementation is a little rough around the edges but I plan to come back and do a lot of refactoring.

The component break-down could have been done better. The CSS could have also been made cleaner and more consistent. I did not have much a consistent approach when using CSS selectors; sometimes I used class names, whilst other times I used a combination of class names and element selectors. I plan to try my hand at Tailwind very soon and think this will result in a more consistent approach.

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

I was having trouble with my font resource loading in the deployed version. At first I was confused and thought it could have been a problem with Vite's resource management during the build step. I have generally included locally stored fonts in the public folder. In this project I decided to experiment with using the /src/assets folder more in order to better take advantage of build optimisations. Vite 'fingerprints' filenames, as well as relocates them during build. I understood that this is handled when we import resources in JS but was unsure if it was handled by referencing a resource in a CSS src: url(). It turns out that it is handled and my problem was in fact due to a filename (unrelated to the fingerprint); it was just due to a mismatch in capitalization between the CSS src and the actual resource.

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

Anything is appreciated!