everyone is running into the same issue with
shared library drift lately. we started seeing our deployment times crawl because everyy single service needs to pull a massive, monolithic utility package just to handle basic logging. it feels like we are building a distributed monolith instead of true microservices. if we keep adding layers of abstraction without auditing what is actually being imported, we will hit a wall. the current strategy of using
npm install @company/core-utils@latest
is clearly failing us now. i want to move toward a pattern where each service only contains the
bare minimum logic required for its specific domain. we should probably implement a strict linting rule to catch unused dependencies before they reach production.
the real problem is usually just bad developer habits regarding imports . does anyone have experience implementing a
lightweight alternative to these massive internal packages? i am thinking about breaking the core utils into smaller, atomic modules like @company/logger and @company/auth-validator. let me know if you have seen this work in a large scale environment without creating a maintenance nightmare.