tsconfigs

What problem does it solve?

It helps you locate where RedisInsight configures TypeScript per area and how to update path mappings so builds, linting, and IDE tooling all stay consistent.

Core Features & Use Cases

• Maps the TS configuration layout across UI, API, Desktop, Storybook, tests, and shared configs so you know exactly which tsconfig to touch.
• Explains alias/resolution requirements for TypeScript, ESLint, Vite, and the Electron/webpack bundle so path aliases work everywhere they’re used.
• Covers common “change scenarios” like adding new path aliases, introducing a new TS folder, and adjusting webpack TS config loading via ts-node.
• Reduces build/lint breakage risk by calling out strict-mode check baselines and CommonJS constraints for ts-node/webpack configs.

Quick Start

Tell the AI what alias or TypeScript folder you want to add, and ask which tsconfig(s) and webpack alias entries must be updated to keep ESLint and builds working.