Track tasks and feature requests
Join 40 million developers who use GitHub issues to help identify, assign, and keep track of the features and bug fixes your projects need.
Sign up for free See pricing for teams and enterprisesDependency hygiene #1687
Dependency hygiene #1687
Comments
This comment has been minimized.
This comment has been minimized.
|
One nice side effect of this effort. So far I've been able to reduce the bundle size by 10KB! From 98338 bytes to 88915 bytes, so far. Should get quite a bit smaller once browserify/browserify#1916 is merged. |
This comment has been minimized.
This comment has been minimized.
Is it worth all the effort put it on this to just reduce the bundle by 10kb? Just asking because my lack of knowledge. |
This comment has been minimized.
This comment has been minimized.
Depends on your priorities. Small size has always been one of my priorities with WebTorrent. It's one of the best parts of WebTorrent – that it's small and carefully selects dependencies. Lots of others decentralized web projects require 2MB+ of JavaScript and don't work nearly as well as WebTorrent does. The fact that we can fit a whole torrent client into <100KB is amazing. Also, updating dependencies gives us bug fixes, wards off potential security issues, and makes installation faster. |
This comment has been minimized.
This comment has been minimized.
|
I recommend using pnpm as the package manager, as it avoids “phantom dependency” and “npm doppelganger” problems by using symlinks, hardlinks and isolated trees. “npm doppelgangers” in particular are a common‑ish cause of exploding bundle sizes. |
This comment has been minimized.
This comment has been minimized.
This is a valid issue that can sometimes happen but I'll be adding a rule to
This is not a problem with |
I want to go through the whole
webtorrentdependency tree to:This issue is a placeholder to track this task.
I'm tracking progress on this work in this issue: brave/brave-browser#5490