0 views collected around this technical thread.
The article explains why removing the massive node_modules folder can take a long time, then shows how to instantly delete it using the rimraf tool, compares rimraf with other deletion commands, and discusses its advantages for Node.js‑based frontend projects.
This article examines the evolution of the three major JavaScript package managers—npm, Yarn, and pnpm—detailing their original designs, the problems they introduced such as nested node_modules, phantom dependencies and doppelgangers, and the innovative solutions like flattening, lock files, symbol/hard links, and PnP mode that each tool brought to improve dependency management.
This article explains how npm installs dependencies, the role of package‑lock.json, the evolution from nested to flat node_modules structures, npm's caching strategy, and provides practical guidance for setting up a private npm registry and handling common installation issues.
The article explains, through a mock interview, why running npm run xxx triggers npm to look up the script in package.json, creates local binary links in node_modules/.bin, and executes the corresponding command such as vue‑cli‑service serve without requiring a global installation.
This article analyzes the slow build process of Dada's massive frontend platform, identifies bottlenecks in dependency installation and webpack compilation, and presents practical optimizations such as node_modules caching, cp command adjustments, Babel loader caching, and other webpack tweaks that reduced average build time from 600 seconds to around 100 seconds.
This article explains the inner workings of npm installation, the differences between npm 2 and npm 3, the purpose and structure of package‑lock.json, and the various dependency types such as dependencies, devDependencies, optionalDependencies, peerDependencies, and bundledDependencies, providing practical guidance for developers.
The article explains that compiling experimental JavaScript features like JSX or class properties inside node_modules tightly couples libraries to build tools, leading to breaking changes, coordination overhead, and prolonged upgrade pain, which is why Create React App avoids such compilation.