Post AZ9LAIXpWMU7NmdnEm by ado@furry.engineer
 (DIR) More posts by ado@furry.engineer
 (DIR) Post #AZ9K3eYjAoMVg6KPku by volpeon@is-a.wyvern.rip
       2023-08-27T07:43:25.900Z
       
       0 likes, 0 repeats
       
       Mastodon still uses Webpack? ​:neofox_googly_shocked:​
       
 (DIR) Post #AZ9L86esk7JhwGtVLc by robinsyl@meow.social
       2023-08-27T07:47:18Z
       
       0 likes, 0 repeats
       
       @volpeon what do you mean "still"? Isn't that relatively new tech?
       
 (DIR) Post #AZ9L8AmTPplYiyTcjg by volpeon@is-a.wyvern.rip
       2023-08-27T07:55:25.783Z
       
       0 likes, 0 repeats
       
       @robinsyl@meow.social I switched to Vite 3 years ago because it was way faster and less complicated than Webpack. Vue also made it their bundler of choice, not sure about other frameworks
       
 (DIR) Post #AZ9LAIXpWMU7NmdnEm by ado@furry.engineer
       2023-08-27T07:48:07Z
       
       0 likes, 0 repeats
       
       @volpeon  maybe their webpack config is a Mobius strip or Klein bottle idk it happened to me once
       
 (DIR) Post #AZ9LAMWYj1qRj04poO by volpeon@is-a.wyvern.rip
       2023-08-27T07:55:51.425Z
       
       0 likes, 0 repeats
       
       @ado@furry.engineer Webpack configs are terrifying ​:drgn_nervous:​
       
 (DIR) Post #AZ9LBKNmAoTDN8QfS4 by digitalfox@yip.vulpine.engineer
       2023-08-27T07:48:36Z
       
       1 likes, 0 repeats
       
       @volpeon With the Rails 7 migration work in Mastodon v4.2.0, maybe that'll be changing soon..?There seems to be a fair bit of technical debt cleanups going on in recent months.
       
 (DIR) Post #AZBHCtkQA1ivqQQzQm by starsider@valenciapa.ws
       2023-08-28T06:14:35Z
       
       1 likes, 0 repeats
       
       @robinsyl @volpeon I used to use webpack and it was neat in the times of v1, lighter and faster than browserify and with many more features, but the ecosystem changed (or maybe our projects just grew) and it became a bloated monster, with breaking changes every major version (it's v5 now). It was a pain in the ass. The worst part is when it inexplicably stopped working in some machines. I had to copy the whole node_modules from a working machine to be able to work, and that trick didn't even work every time.Note that it was made for the times when JS modules didn't exist, and got stuck on the mindset where making a bundle was the ONLY way to make it work in the browser.Nowadays I just use modules directly for development (zero build time) and rollup for deployment (and development in some cases). That's if I'm using JS at all. Modern bundlers like vite do this under the hood, but I just don't even bother with that. I guess I got burnt out too much with webpack.
       
 (DIR) Post #AZBJnq3D4JVR09xt0i by crumbcake@meow.social
       2023-08-28T06:49:29Z
       
       0 likes, 0 repeats
       
       @robinsyl @volpeon JS tech has the same lifespan as a moth. I'm convinced that half the time websites do a "new UI" it's because their old frontend became such an unmaintainable mess that they physically could not continue to develop on it.Hell I built a web frontend last Friday that's already on track to be deprecated by the end of next week.