skills.rest
stacksjs
stacksjsOFFICIAL
Explore all skills by this author →
Website𝕏@stacksjsGitHub

stacks-alias

Apply @stacksjs/* path alias mappings across Stacks workspace packages and TypeScript configurations.

622|17|Updated Apr 26, 2022
Search Tags:#typescript#monorepo#alias#build-system#path-resolution#import-resolution
One-click install
npx skills add https://github.com/stacksjs/stacks --skill stacks-alias
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: stacks-alias
Source: https://github.com/stacksjs/stacks/tree/main/.claude/skills/stacks-alias
Command: npx skills add https://github.com/stacksjs/stacks --skill stacks-alias

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Simplifies configuring and maintaining path aliases in Stacks projects to ensure reliable imports across packages.

Core Features & Use Cases

  • Centralized alias configuration for all Stacks packages to guarantee consistent module resolution.
  • Maps @stacksjs/* imports to workspace paths, aligning TypeScript paths with the monorepo layout.
  • Works with TypeScript and Bun module resolution to support both build and runtime environments.
  • Useful for debugging and validating alias configurations across large codebases.

Quick Start

Configure path aliases for your Stacks monorepo and verify alias resolution across packages.

Frequently Asked Questions about stacks-alias

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

FAQPage Schema
How do I configure path aliases for TypeScript imports in a monorepo?▼

Path alias resolution for Stacks imports maps @stacksjs/* module identifiers to workspace paths. It aligns TypeScript path configurations with the monorepo layout to ensure consistent imports across all workspace packages.

Does Bun module resolution work with TypeScript path aliases in a monorepo?▼

Alias configuration supports both TypeScript and Bun module resolution to ensure imports resolve correctly across build and runtime environments within Stacks monorepos.

Why are my @stacksjs/* imports not resolving correctly across workspace packages?▼

Import resolution fails when TypeScript paths and monorepo layouts are misaligned. This Skill validates alias configurations, applies correct @stacksjs/* path mappings, and provides troubleshooting guidance to resolve import errors.

What is the best way to manage import path aliases across multiple workspace packages?▼

Centralized alias configuration maps @stacksjs/* imports to workspace paths, aligning TypeScript configurations with the monorepo layout to guarantee consistent module resolution across all packages.

How do I validate and troubleshoot path alias configurations in a large codebase?▼

Validating alias configurations involves verifying module resolution across workspace packages. This Skill documents validation steps and troubleshooting guidance to debug and verify path aliases across large codebases.

Related Skills

Explore More Software Engineering Skills→
marcioaltoemarcioaltoe
14

barrel-craft

Generate barrel files to consolidate exports in TypeScript/React projects.

Community
Intermediate
h-4vokh-4vok

repo-validate

Run lint, typecheck, test, smoke, and build checks across a repository and emit a pass/fail report.

Community
Intermediate
Jeff-StapletonJeff-Stapleton
1

microfrontend-nx

Standardize microfrontend development in NX monorepos with Module Federation.

Community
Advanced
bughqbughq
2

stacks-alias

Resolve StacksJS file paths to standardized @stacksjs/ and ~ aliases.

Official
Intermediate