Dependency ↔ extra external code that a project/Source Code depends on to work

aka Dependencies, Deps

Cyclical Dependency

References

1. /node_modules ↔ dir with all Deps & their sub-Deps & their sub-sub-Deps & ...

2. to maintain legacy codebase ↔ for compat with older Deps, legacy code & outdated coding syntax

3. Dependency Hell ↔ of project with clusterfuck Deps or ver compat issue 🍜👨‍💻 PAIN to run/migrate, stuck with outdated code

4. package.json ↔ Manifest to def project Metadata, Deps & scripts

5. Standalone ↔ redux lib has no Deps

6. Deps Array ↔ Deps[] to pass as last arg to Trigger Hook

7. Package Manager ↔ Dev tool to auto install/update/remove Package & Deps

8. Zero Deps ↔ of vanilla (JS/Programming Language/Binary) Lib to run out-of-box w/o req external Deps

9. Docker Container Image ↔ immutable snapshot of Software & Deps-tree down to OS-layer (everything req to run App)

10. pnpm import ↔ to import Deps from npm/yarn lock-files into pnpm-lock.yaml

11. to reduce bundle size ↔ keep Deps on Server Component, min Bundle for Client

12. Microservice vs Monolith ↔ steep setup pays off - decouple Deps to allow lang agnostic, speed up DevOps pipeline & isolate risk. Latency?

13. pnpm add -D nodemon ↔ to add nodemon as dev Deps - must be capital flag!! else default to normal depedency list with pnpm

14. react-router ↔ core Deps import by react-router-dom for Browser or react-router-native for mobile - always use react-router-dom for desktop/web!

15. Inversion of Control ↔ Design Pattern to invert Control Flow to Callback to increase Modularity & decouple Deps ??