I've started using Perfume.js on this site to capture web performance metrics including Core Web Vitals. As part of this, I wanted to create a flexible logging tool that would help me send this data to my Supabase backend but also handle logging any other performance data in the future, and heck, handle anything I might want to log!
I love the RESTful API generated automatically by PostgREST from my Supabase PostgreSQL schema. However, at the beginning I did have concerns about how I could handle more complex queries … that was at least until I read more about PostgreSQL Functions and how to build them in Supabase!
I've found it useful in the past to keep a close eye on build times because it can be easy to introduce code over time that drives the build time up. By the time you notice that this is becoming a pain point, it's very difficult to track down the offending pieces of code to resolve the issue.
My previous post walked through my progress with swapping Webapck for Vite using the Middleman external pipeline. I was able to quickly see great performance improvements, reduced dev server and build times and a decent drop in the number of JavaScript dependencies. But there were still some issues and I knew I could improve things. Especially after I discovered Vite Ruby.
I have been using the Middleman external pipeline with Webpack to bundle my JavaScript and SCSS files and this approach has been working well after I eventually worked my way through all of the complexities of the initial Webpack configuration. But with so many bundlers available at the moment I thought it was time to see how things could be improved.
My last blog post demonstrated how to build a JavaScript documentation website using JSDoc and have it deployed on Netlify. The process was a bit manual though so in this post I improve upon the solution by automating the build using a GitHub Action to ensure my documentation website is never out of sync with the documentation in my code base.
I think code documentation works best when it lives side by side with the code it is documenting rather than being written in a separate document. When it's separate, it becomes easy for documentation to become stale. Out of sight, out of mind!
Have you struggled to figure out a good way to test your Netlify Functions? As you start to make more use of functions, you really need to have good unit tests in place for peace of mind during production deploys.
Netlify Functions are a fantastic way to extend the capabilities of a static site and enable you to easily build scalable and dynamic applications.
Core Web Vitals are all the rage right now because of effect they might have on search rankings. I'm passionate about website performance and thought it might be nice to make more of a feature of Core Web Vitals on my personal site.