BundlePhobia mentions (51)

• How We Went from 46 to 99 Performance Score to Improve Our Website Speed

  There are some handy tools for identifying and addressing problematic bundles. One of them, Bundlephobia, gives insights into how much an NPM package contributes to bundle size, helping avoid too large collections of files. Import Cost, a VSCode Extension, calculates the 'cost' of imported packages, helping to make informed decisions. As part of our optimization strategy, we've swapped out hefty JS libraries, such... - Source: dev.to / 11 days ago

• JavaScript Habits That Grind My Gears

  So, before adding a dependency to your projects, ask yourself if you truly need it and check how much a package weighs. If you would like to go through cleaning up process, I wrote an article on optimizing Next.js bundle size on my private blog. - Source: dev.to / 9 months ago

• 3 online tools to use for selecting a future-proof NPM library for frontend and Nodejs projects

  🔴 https://bundlephobia.com/ - estimate a footprint, basically how many Kb will be added to your bundle when you add this dependency to your project. Those may differ a lot, try comparing say - dayjs vs momentjs ;. - Source: dev.to / 10 months ago

• Tiptap vs remirror installation sizes

  I have phobia of dependencies and package sizes, so tiptap is 62KB and remirror is 150KB. Not much difference, since difference is no in MB's. Source: 10 months ago

• Add stepper components to your React app

  External packages increase your app bundle size (you can calculate this using BundlePhobia), so adding a third-party package for every development requirement isn’t always a good choice. Also, third-party packages may not completely fulfill your design requirements and may bring features that you don’t even use. Writing your own stepper component is also an option by including only the required features. - Source: dev.to / about 1 year ago

Google Fortune Telling mentions (0)