skills.rest
spencerbeggs
spencerbeggsCOMMUNITY
Explore all skills by this author →
GitHub

effect-api-extractor-bases

Resolve ae-forgotten-export CI errors for Effect class factories using inline heritage patterns and scoped TSDoc suppression in TypeScript builds.

2|Updated Jul 2, 2026
Search Tags:#typescript#monorepo#effect#tsdoc#build-tooling#api-extractor
One-click install
npx skills add https://github.com/spencerbeggs/effected --skill effect-api-extractor-bases
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: effect-api-extractor-bases
Source: https://github.com/spencerbeggs/effected/tree/main/plugin/skills/effect-api-extractor-bases
Command: npx skills add https://github.com/spencerbeggs/effected --skill effect-api-extractor-bases

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill resolves the ae-forgotten-export CI-fatal errors that occur when using Effect class factories like Schema.Class or Context.Service, which produce anonymous heritage types that API Extractor cannot automatically resolve.

Core Features & Use Cases

  • Factory Inlining: Provides the standard policy for inlining class factories to prevent synthesized symbol leaks.
  • Scoped Suppression: Guides the implementation of narrow, principled TSDoc suppression for _base symbols.
  • TSDoc Resolution: Offers specific strategies for resolving complex TSDoc link issues, including merged value-type names and cross-package symbols.

Quick Start

Apply the inline factory pattern and add the _base suppression to your savvy.build.ts file to resolve the forgotten export warning.

Frequently Asked Questions about effect-api-extractor-bases

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

FAQPage Schema
Why does API Extractor report ae-forgotten-export errors for Effect class factories?▼

API Extractor reports ae-forgotten-export errors for Effect class factories because Schema.Class and Context.Service generate anonymous heritage types that the tool cannot automatically resolve. Inlining factory patterns prevents synthesized symbol leaks during TypeScript monorepo builds.

How do I resolve ae-forgotten-export warnings in a TypeScript monorepo using the silk bundler?▼

To resolve ae-forgotten-export warnings, apply the inline factory pattern to your Effect classes and add scoped _base TSDoc suppressions in your savvy.build.ts file. This enforces strict zero-warning issues.json outputs for production builds.

What is the best way to suppress TSDoc link errors for Effect _base symbols in API Extractor?▼

The best way to suppress TSDoc link errors for Effect _base symbols is to implement narrow, principled TSDoc suppression. This targets only the necessary base symbols to resolve complex merged value-type names and cross-package symbol issues.

Does this API Extractor fix for Effect apply to version 4 libraries?▼

Yes, this API Extractor fix applies to Effect v4 libraries. It is designed for monorepo build pipelines using the silk bundler to satisfy strict production build requirements for zero-warning issues.json outputs.

How do inline heritage patterns fix API Extractor diagnostics for Schema.Class?▼

Inline heritage patterns fix API Extractor diagnostics by explicitly defining the class structure instead of relying on synthesized factory outputs. This prevents anonymous heritage types from triggering ae-forgotten-export errors in TypeScript projects.

Related Skills

Explore More Software Engineering Skills→
MyHeavenDyfMyHeavenDyf

effect

Provide TypeScript code examples for Effect v4 typed services and workflows.

Community
Intermediate
Mte90Mte90
51

Error Handling

Define Golang error wrapping and checking standards using Go 1.13+ errors package.

Community
Intermediate
TheSpiciestDevTheSpiciestDev

nx-plugins

Discover, install, and integrate Nx plugins within a monorepo.

Community
Basic
tassiovaletassiovale
13

matplotlib

Create custom Matplotlib visualizations for data analysis and publication.

Community
Advanced