Introduction#
Hello everyone,
How are you? Welcome to my blog. In this post, I will talk about Futtun’s progress update, from Monday 16 February 2026 to today, Sunday 22 February 2026.
Launched Futtun#
It only took me 8 weeks (I am being sarcastic), but I have finally launched Futtun, at https://www.futtun.com.
It is my first time deploying a React app, and I am pleased to say it was less of a headache than I anticipated it to be. I have a blog post in the works detailing what I did to deploy Futtun, where I will explain the what and the why in more detail.
Dependency upgrades#
Since Futtun is now on the Internet, I need to keep its dependencies up to date, to avoid security incidents.
Fix tests after upgrading vitest-react-browser#
I am using vitest as the testing framework, which in turn uses vitest-react-browser to integrate with React. Updating the latter to 2.0.5 surfaced some bugs due to not awaiting certain actions in the tests (render and cleanup). I should have used await on them, and after doing so, tests are back to passing.
Started work on keeping an audit log for Futtun#
One of my goals with Futtun is to have a log of every action the user takes, and recreate a user’s data based on this log.
Since Futtun lives only in the user’s browser, when the user cleans their browser’s data, Futtun loses what the user recorded on it. By having an audit log that the user can download, I can work around this issue. The flow I envisage is the following:
- Users download this audit log file;
- Users upload this audit log file to Futtun;
- Futtun parses it, and re-creates the user’s data based on it.
I refrained from implementing this audit log from the beginning, because I was new to React. First, I wanted to familiarise myself with React, and only implement this log once I gained some confidence with these new to me tools.
Conclusion#
Thank you for your time, and I hope to see you again soon. Bye bye.