spend a whole day trying to get webpack to work properly. #adam

spend another 2 hours because recent versions of next.js have a bugged hmr

Spend almost 2 hours to figure out how to run GA in Nextjs and TypeScript #whattodoinmallorca

Spend all day debugging/researching auth cookies issue in Next.js #stronger

Try to get NextJS working

get nextjs apis working (was a pain, took 1hr cuz I'm dumb af...) #inpilot

Spent some time learning NextJS and Express

Work on #buildstreak Finish migration to Next.JS 13. Don't know if I'm way overengineering this sideproject and should reduce scope and juist build my own product instead but I've already invested a lot of time (while learning a lot). Struggling between making it technically good and just getting something out of the door as a one guy noob dev.

finally start working on site after hours of troubleshooting in nextjs #newproject

livecode messing around with nextjs #codewithswiz

give up using nextJS for #aitoolsfor and moving back to trusty rails to move faster

livecode trying out NextJS #codewithswiz

first time playing around w next.js #studydev

Waste even more time with webpack. Probably got to the other side of the tunnel #perspectiva

#contracting Spontaneously upgrade from Timber 1.22 to Timber 2.0 and spend 3 hours suffering through the extensive upgrade guide 🥲

Waste too much time with webpacker #perspectiva

Spent 30 minutes reading 'Testing Vue.js Applications', stopped at 2.1.4 #rhymecraft

Give up on nextjs. Started migrating away from nextjs because I have wasted tons of hours on trying to fix authentication using supabase

Spent an hour reading some of [the backend code][1] for a Go / Vue chat app I saw posted to Reddit, as a way of trying to build familiarity with how my Go / Vue projects should be structured / work. [1]: github.com/wizzldev/backend/

Spent time researching whether to switch the app to use Nuxt.js for server-side rendering / static site generation. #rhymecraft