3 ms·
Exactly. Let's say Eslint, TS, Prettier, Jest, and Webpack, are just standard for most projects I start. The problem is, each little issue a developer has, oft
by topicseed 6y ago
Exactly. Let's say Eslint, TS, Prettier, Jest, and Webpack, are just standard for most projects I start.
The problem is, each little issue a developer has, often requires not just installing these, but then adding a whole bunch of plugins to make them work together. So whenever I start a project, my package.json is just already packed with a gazillion of devDependencies from @types/ to eslint and webpakc plugins.
- wildpeaks 6y agoThis is the reason why I wrapped my Webpack config in its own package (same with Eslint), that way I pretty much only have a single dependency to add when starting or maintaining a project (and if a project has a very unique need, it can still modify the config generated by the package). The package has a bunch of automated tests, so Dependabot checks for me if dependency updates are still compatible with the way I expect them to behave (and if a dependency needs to be swapped by another, I only need to do it in one place).