bun-effect-monorepo-tsconfig

Configure TypeScript for Bun monorepos using Effect-TS.

Updated Jul 7, 2026
One-click install
npx skills add https://github.com/TitoPrausee/nexus-toti --skill bun-effect-monorepo-tsconfig
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bun-effect-monorepo-tsconfig
Source: https://github.com/TitoPrausee/nexus-toti/tree/main/data/skills/devops/bun-effect-monorepo-tsconfig
Command: npx skills add https://github.com/TitoPrausee/nexus-toti --skill bun-effect-monorepo-tsconfig

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the friction of getting TypeScript to work cleanly in Bun monorepos that use Effect-TS, especially when typechecking breaks on workspace resolution, iteration semantics, or shared config inheritance.

Core Features & Use Cases

  • Bun-compatible TypeScript setup: Recommends the compiler options that match Bun's runtime and package resolution model.
  • Effect-TS compatibility fixes: Addresses common errors caused by iterable effects, library type conflicts, and mismatched module settings.
  • Monorepo troubleshooting: Helps when workspace packages fail to resolve, shared tsconfig settings leak into child packages, or stale build artifacts break tests.
  • Use Case: A team can apply this guidance to stabilize a multi-package Bun repository where typechecking fails after adding new workspace packages or database libraries.

Quick Start

Ask for a Bun and Effect-TS monorepo tsconfig fix that makes typechecking pass without breaking workspace imports.

Frequently Asked Questions about bun-effect-monorepo-tsconfig

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

FAQPage Schema
How do I fix TypeScript configuration failures in a Bun monorepo using Effect-TS?

Fix TypeScript configuration failures in a Bun monorepo using Effect-TS by applying compiler options for bundler module resolution, ESNext modules, downlevelIteration, noEmit, and bun types to ensure reliable typechecking and workspace package resolution.

Why does my Bun monorepo typechecking break after adding new workspace packages?

Bun monorepo typechecking breaks when workspace packages fail to resolve due to missing explicit workspace dependencies or leaked shared tsconfig settings. Fix this by enforcing explicit workspace dependencies and proper shared tsconfig inheritance across multi-package repositories.

What compiler options are required for Effect-TS compatibility in a Bun workspace?

Effect-TS compatibility in a Bun workspace requires compiler options including bundler module resolution, ESNext modules, downlevelIteration, noEmit, and bun types to address common errors caused by iterable effects and mismatched module settings.

How do I prevent shared tsconfig settings from leaking into child packages in a Bun monorepo?

Prevent shared tsconfig settings from leaking into child packages in a Bun monorepo by configuring proper shared tsconfig inheritance across multi-package repositories and ensuring workspace package resolution matches Bun's runtime and package resolution model.

Does Effect-TS work with Bun's module resolution model?

Effect-TS works with Bun's module resolution model when TypeScript configuration uses bundler module resolution, ESNext modules, and downlevelIteration to address common errors caused by iterable effects and library type conflicts.

What causes iterable typing errors in Effect-TS when using a Bun monorepo?

Iterable typing errors in Effect-TS within a Bun monorepo are caused by mismatched module settings and missing downlevelIteration. Fix these errors by applying Bun-compatible TypeScript setup with ESNext modules and bundler module resolution.