Kuan

October 2, 2022

Use bleeding edge tools, bleeds.

It is fun riding on the hype of the latest, shiny and paradigm shifting tools to build my boring web application. SvelteKit is still in early stage, but I loved Svelte so much I launch the next project with it as soon as I gave myself enough excuse to start yet another project.

The bleeding edge nature of SvelteKit already bite me once. That was when they locked down version 1.0.0 and did a big refactoring on their routing. Which took a very different naming convention on files and folders. I was outdated for too long (like 2 months?). My project is in total mess trying to "upgrade".

I ended up create a brand new project with the latest SvelteKit and copied whatever I can savage from the old project. It isn't that bad. That old project was started as a test project anyway. Still sucks to not able to upgrade in place.

Blood number 1.

Today is sort of blood number 2. Two weeks not touching my SvelteKit project, came back to it today to work on some session/cookie/local storage thingy. Following the documentation and found out that I am having undefined problem with a `cookie` parameters. Hmmmmph. What could be wrong?

Turns out. The guide I was following is 2 weeks old, and the documentation about the new cookie is lack luster because this is a new feature that replaced the old `getSession` API, launched just in a month. So many issues about it are still one week old. And I thought I was using a very stable feature.

Wasted almost half a day for it. BLOOD and DARKNESS!

About Kuan

Web developer building with Flutter, Svelte and JavaScript. Recently fell in love with functional programming.

Malaysian. Proud Sabahan. Ex game developer but still like playing games.

New found hobby is outdoor camping with my love.