Fixed stupid issue with Webpack build fails because CSS files reference images using output paths (../../static/images/) instead of source-relative paths (../images/). dumb dumb dumb very dumb #ddswitch

Stuck on trying to remove webpack.

Lots have changed in Rails / Webpack in the last year, so decided to ditch Webpack completely and go with Vite instead ⚡️ #tijdwerk

figure out webpack 4 => 5 migration with all the weird deprecated plugins that needed replacement

remove webpack. #cyberjobs

accept webpacker as required, for now

hate webpacker

Finally remove webpack the piece of garbage it is #wip

transformation of the webpack extension quickly, which allows to use vue 3 and tailwind also in the chrome extension #socialsellingai

fixed webpack / nextjs support of graphql files #thrust

update to webpack 5 #pm

Merge "search functionality" bundle into main webpack bundle, so Turbolinks works correctly again between page loads #startupjobs

Use webpack's splitChunks to only serve the packs the client needs (e.g. rich text editor isn't needed for most visitors) #startupjobs

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

Setup webpack and LiveViews #clanlatamdb

getting everythhing in webpack to work & save it as template #adam

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

hook into Webpack Hot Module replacement to refresh data after #devsync

get #devsync working with Webpack boilerplate and improve source path assignment

#pintura add cache bust to webpack build of product site