If you want to benchmark yourself when you learn React. I’ve completed most of the medium/hard react problems at https://practice.dev to get my job. Source: over 2 years ago

It took me a few months to build practice.dev. Here I extracted the IDE and added live collaboration and npm resolver. It took me 1 week to release live-ide.dev. Source: over 2 years ago

The idea of practice.dev is to create basics tutorials (currently it's in progress) similar to FreeCodeCamp, and create hundreds of challenges with greater difficulty. Think of it like leetcode/codewars for frontend. Source: almost 3 years ago

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 / 8 months ago

🔴 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 / 9 months ago

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

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

For web projects, there is a great tool to determine package sizes: Bundlephobia. Of course, server-side rendering and tree shaking might reduce the size, but this needs to be always verified. - Source: dev.to / about 1 year ago