I had my website deployed as a virtual host using web station. Then I moved it into a virtual DSM where I setup web station and backends etc. Exactly the same (restored a hyper backup of web station and website files/databases into the VM then uninstalled same from the main NAS). Then to get to it over the web, my NAS has a reverse proxy that routes the traffic to the VM. The way it's setup the only port that will... Source: almost 2 years ago

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

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

🔴 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

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