21 replies

1. Lou Cyx Mastodon 7 min later

   @zachleat there are so many things that can be done with native forms and inputs and folks are still using formik and libraries like it. I constantly advocate for folks to use the platform, but it's such an uphill battle sometimes 😣

2. Private reply Mastodon 9 min later
   1. Private reply Mastodon 1 hr later
      1. Private reply Mastodon 17 hr later
3. Alvaro Montoro Mastodon 18 min later

   @zachleat 352KB for a script that resizes textareas? What spying is it doing with the remaining 350KB?

4. Matt Wilcox Mastodon 1 hr later

   @zachleat “Can” doing a lot of work there

5. Ben Schwarz Bluesky 1 hr later

   Problem is: it probably won’t. React devs seem to wear blinkers when it comes to CSS functionality. Pretty hard when you’ve had a virtual dom lobotomy 😵‍💫

6. Dominik 🔮 Bluesky 7 hr later

   All for it, but please, 352kb is the install size. Bundle size is 1.6kb minzipped.

   1. Nick Williams Bluesky 13 hr later

      Wish these tools did a better job at presenting bundled size

      1. Dominik 🔮 Bluesky 14 hr later

         depends on a lot of things though, like the bundler or if deps are bundled or excluded etc..

         1. Nick Williams Bluesky 15 hr later

            Yeah not an easy problem. Should include non-peer deps at least

   2. Zach Leatherman Bluesky 14 hr later

      hm? bundle size isn’t the only important concern worth scrutinizing (though stating bundle size independent of dependency/library bundle cost is one of my mildest pet peeves 😅)

      1. Dominik 🔮 Bluesky 14 hr later

         If someone reads:

         > This 352.8 kB react component

         Then the first instinct will be that 350kb will be shipped to consumers if I use that component. That’s not the case, so why frame it that way?

         1. Mark Erikson Bluesky 15 hr later

            that's always been my biggest annoyance with package listings on NPM (and now seemingly NPMX). Yes, download size and install size in node_modules matter... but those are often radically different than bundle size shipped to the browser, and that doesn't get surfaced very well.

         2. Zach Leatherman Bluesky 15 hr later

            ahh, hmm — that’s a fair critique of my post. it looks like bundle versus install weight is a pet peeve of yours! 😅

            1. alan Bluesky 19 hr later

               I definitely read it as 325kb shipped to browser. I get both numbers are worth considering, but if I'm only gonna get one, I want the one that impacts the folks using my site over the one during dev.

               (in this case just the fact that you can remove it is cool enough for me regardless of size impact)

   3. Konnor Rogers Bluesky 15 hr later

      I'm curious where you got 1.6kb. Is that locally with treeshaking or something?

      I see 5.26kb gzipped on bundlejs

      bsky.app/profile/konn...

      Quoted post

      1. Zach Leatherman Bluesky 15 hr later

         likely excluding peerdeps zachleat.github.io/bundlewhys/?...

         1. Konnor Rogers Bluesky 15 hr later

            Ahhh. That'll do it

            1. Dominik 🔮 Bluesky 15 hr later

               Yeah I got it from bundlephobia which is usually too large because it doesn't do esm I think

7. Konnor Rogers Bluesky 15 hr later

   fwiw whats actually shipped to the browser for this library is 13.6kb (5.26kb gzipped)

   bundlejs.com?q=react-text...