What is the 'Module Resolution' strategy and how do 'paths' work in tsconfig?

Module resolution is the process the compiler uses to figure out what a 'require' or 'import' refers to; 'paths' allow for custom aliasing.

TypeScript supports two strategies: 'Node' (mimics Node.js logic) and 'Classic'. Modern projects use 'Node' or 'Bundler'. The paths property in tsconfig.json allows you to create aliases for long relative paths (e.g., @app/* mapping to src/*). This makes code cleaner and easier to refactor, but requires a corresponding configuration in your bundler (like Webpack or Vite) to work at runtime.