skills.rest
redis
redisOFFICIAL
Explore all skills by this author →
WebsiteGitHub

tsconfigs

Locate and update RedisInsight TypeScript configuration files and path aliases.

8.7k|482|Updated Jul 30, 2021
Search Tags:#typescript#eslint#webpack#vite#tsconfig#ts-node#path aliases
One-click install
npx skills add https://github.com/redis/RedisInsight --skill tsconfigs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tsconfigs
Source: https://github.com/redis/RedisInsight/tree/main/.ai/skills/tsconfigs
Command: npx skills add https://github.com/redis/RedisInsight --skill tsconfigs

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about tsconfigs

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I update TypeScript path aliases across tsconfig, ESLint, and webpack?▼

To update TypeScript path aliases safely, you must mirror new desktop imports into webpack resolve.alias entries, update tsconfig path mappings, and ensure ESLint parserOptions.project auto-discovery points to the correct per-area configuration.

Why does ESLint fail to resolve path aliases after adding a new TypeScript folder?▼

ESLint fails to resolve path aliases when parserOptions.project auto-discovery cannot locate the new folder's tsconfig. You need to verify the per-area tsconfig ownership model and ensure includes and path mappings are defined for that specific area.

How does ts-node load webpack TypeScript configs without breaking CommonJS constraints?▼

ts-node loads webpack TypeScript configs by adhering to CommonJS constraints and strict-mode check baselines. Adjusting webpack TS config loading requires referencing the per-area tsconfig ownership model to prevent build breakage.

Where are tsconfig and path mappings defined for different areas like UI, API, and Storybook?▼

TypeScript configurations are defined using a per-area tsconfig ownership model, mapping separate layouts across UI, API, Desktop, Storybook, and tests so you know exactly which configuration file to modify.

What's the best way to add a new TypeScript area and keep Vite and IDE tooling consistent?▼

The best way to add a new TypeScript area is to update the per-area tsconfig includes and path mappings, then mirror those desktop imports into webpack resolve.alias so Vite, ESLint, and builds all stay consistent.

Related Skills

Explore More Software Engineering Skills→
virajpvirajp
1

tsconfig

Standardize TypeScript compiler configuration layouts for single packages and pnpm monorepos.

Community
Intermediate
Kinfe123Kinfe123
35

build-pipelines-bundling

Explains bundling, code splitting, tree shaking for Webpack, Vite, esbuild.

Community
Advanced
Mte90Mte90
51

TypeScript Tooling

Configure ESLint, Prettier, Jest, and build tools for TypeScript projects.

Community
Intermediate
pantheon-orgpantheon-org
9

nx-vite-integration

Configure Vite as the build tool within Nx monorepos.

Official
Intermediate