@capillarytech/blaze-ui 5.21.0 → 5.22.0

package/CapForm/tests/USE_CASES_ANALYSIS.md

@@ -1,119 +0,0 @@
-# CapForm Use Cases Analysis
-
-## Component Overview
-CapForm is a wrapper around Ant Design v5 Form component that adds:
-- Custom wrapper div with styling (`cap-form-wrapper`)
-- Default layout of 'vertical'
-- Custom className support
-- Passes through all Ant Design FormProps
-
-## Phase 1: Use Cases NOT Currently Fulfilled
-
-### 1. Form Instance Access
-**Status**: ⚠️ Not Explicitly Documented/Tested
-**Issue**: Component doesn't expose Form instance methods (getFieldsValue, setFieldsValue, validateFields, etc.) in a convenient way
-**Current Behavior**: 
-- Form instance is available via `Form.useForm()` hook, but CapForm doesn't provide a ref or instance prop
-- Users must use Ant Design's Form.useForm() hook separately
-
-**Expected Behavior** (if required):
-- Provide form instance via ref forwarding
-- Or expose form methods through a prop
-
-**Recommendation**: Document that users should use `Form.useForm()` hook and pass `form` prop to CapForm, or add ref forwarding if needed.
-
-### 2. Form List/Dynamic Fields
-**Status**: ✅ Supported (via Ant Design Form.List)
-**Note**: Component passes through all FormProps, so Form.List should work, but it's not explicitly tested or documented in CapForm context.
-
-**Recommendation**: Add test cases and examples for Form.List usage.
-
-### 3. Form Dependencies (shouldUpdate, dependencies)
-**Status**: ✅ Supported (via Ant Design Form.Item dependencies)
-**Note**: Component passes through FormProps, so dependencies work, but not explicitly tested.
-
-**Recommendation**: Add test cases for form field dependencies.
-
-### 4. Custom Validation Rules
-**Status**: ✅ Supported (via Ant Design Form.Item rules)
-**Note**: Component passes through FormProps, so custom validation rules work via Form.Item, but not explicitly tested at CapForm level.
-
-**Recommendation**: Add test cases demonstrating custom validation.
-
-### 5. Form Reset Functionality
-**Status**: ✅ Supported (via Ant Design Form instance methods)
-**Note**: Form reset is available via form instance methods, but not explicitly tested.
-
-**Recommendation**: Add test cases for form reset scenarios.
-
-### 6. Form Field Value Watching
-**Status**: ✅ Supported (via Ant Design Form.Item shouldUpdate or Form.useWatch)
-**Note**: Component supports this via Ant Design APIs, but not explicitly tested.
-
-**Recommendation**: Add test cases for value watching scenarios.
-
-### 7. Form Submission Loading State
-**Status**: ⚠️ Not Built-in
-**Issue**: No built-in loading state management during form submission
-**Current Behavior**: 
-- Users must manage loading state manually
-- No `loading` prop on CapForm
-
-**Expected Behavior** (if required):
-- Add `loading` prop that disables form during submission
-- Or provide loading state management helper
-
-**Recommendation**: This is typically handled at application level, but could be a convenience feature.
-
-### 8. Form Validation Feedback Timing
-**Status**: ✅ Supported (via Ant Design validateTrigger)
-**Note**: Component passes through FormProps, so validateTrigger works, but not explicitly tested.
-
-**Recommendation**: Add test cases for different validation trigger scenarios (onChange, onBlur, onSubmit).
-
-### 9. Nested Forms
-**Status**: ⚠️ Not Recommended/Tested
-**Issue**: Ant Design doesn't officially support nested forms, and CapForm doesn't prevent or handle this
-**Current Behavior**: 
-- Nested forms may cause unexpected behavior
-- Not tested or documented
-
-**Recommendation**: Document that nested forms are not supported and may cause issues.
-
-### 10. Form Field Array Operations
-**Status**: ✅ Supported (via Ant Design Form.List)
-**Note**: Component supports Form.List for dynamic fields, but array operations (add, remove, move) are not explicitly tested.
-
-**Recommendation**: Add test cases for Form.List add/remove/move operations.
-
-## Test Coverage Summary
-
-The comprehensive test suite covers:
-✅ Default rendering and initialization
-✅ Layout variations (horizontal, vertical, inline)
-✅ Custom className application
-✅ Form callbacks (onFinish, onFinishFailed)
-✅ Initial values handling
-✅ Form props passthrough (size, requiredMark, colon, preserve, labelCol, wrapperCol, scrollToFirstError)
-✅ User interactions (form submission, input changes)
-✅ Edge cases (empty form, null/undefined children, multiple classNames)
-✅ Accessibility (form role, ARIA attributes, keyboard navigation)
-✅ Data flow and state management (re-renders, initialValues changes)
-✅ Conditional rendering
-
-## Recommendations
-
-1. **High Priority**: Add test cases for Form.List (dynamic fields)
-2. **High Priority**: Add test cases for form instance methods (getFieldsValue, setFieldsValue, validateFields, resetFields)
-3. **Medium Priority**: Add test cases for form field dependencies
-4. **Medium Priority**: Add test cases for custom validation rules
-5. **Low Priority**: Consider adding loading state prop if commonly needed
-6. **Low Priority**: Document form instance usage patterns
-7. **Low Priority**: Add test cases for validateTrigger variations
-
-## Notes
-
-- CapForm is a thin wrapper around Ant Design Form
-- Most functionality comes from Ant Design FormProps passthrough
-- Component focuses on styling and default layout configuration
-- All Ant Design Form features are available but may need explicit testing/documentation

package/CapFormItem/README.md

@@ -1,320 +0,0 @@
-# CapFormItem Migration Guide
-
-## Summary
-
-CapFormItem has been migrated from `cap-ui-library` to `blaze-ui` with the following changes:
-
-- Converted from JavaScript to TypeScript
-- Converted from styled-components to SCSS modules
-- Migrated to Ant Design v6 APIs
-- Added TypeScript interfaces for props
-- Maintained backward compatibility with the existing API
-
-## Breaking Changes
-
-**No breaking changes from cap-ui-library v8.x**
-
-The component maintains full backward compatibility with the existing API. All props from the original component continue to work as expected.
-
-## Ant Design Component Used
-
-CapFormItem wraps the **Form.Item** component from Ant Design v6.
-
-### Form.Item Props Status
-
-**✅ No deprecated props**: The `Form.Item` component from Ant Design v6 does not have any deprecated props according to the [Ant Design v6 Migration Guide](https://ant.design/docs/react/migration-v6). All Form.Item props remain valid and unchanged in v6.
-
-## Deprecated Props
-
-**None** - There are no deprecated Ant Design props for Form.Item in Ant Design v6.
-
-The following Ant Design components have deprecated props in v6, but **Form.Item is not among them**:
-- Dropdown: `visible` → `open`, `overlayClassName` → `classNames.root`, `overlay` → `menu`
-- Tooltip: `destroyTooltipOnHide` → `destroyOnHidden`, `overlayClassName` → `classNames.root`
-- Tabs: `TabPane` children → `items` prop, `tabPosition` → `tabPlacement`
-- Alert: `message` → `title`
-
-**Note**: CapFormItem only uses `Form.Item`, which has no deprecated props in v6.
-
-## Prop Changes
-
-### CapFormItem Props
-
-CapFormItem extends `FormItemProps` from Ant Design v6 and adds the following props:
-
-| Prop | Type | Default | Description |
-|------|------|---------|-------------|
-| `className` | `string` | `undefined` | Additional CSS class name |
-| `children` | `React.ReactNode` | - | Form control children (e.g., CapInput, CapSelect) |
-| `label` | `string` | `undefined` | Label text for the form item |
-| `required` | `boolean` | `false` | Whether the field is required |
-| `help` | `string` | `undefined` | Help text to display below the field |
-| `validateStatus` | `'success' \| 'warning' \| 'error' \| 'validating'` | `undefined` | Validation status |
-
-### All Form.Item Props Supported
-
-CapFormItem accepts all props from Ant Design's `FormItemProps`, including:
-
-- `name` - Field name for form data binding
-- `rules` - Validation rules
-- `dependencies` - Field dependencies
-- `shouldUpdate` - Custom update logic
-- `initialValue` - Initial field value
-- `noStyle` - Remove wrapper styles
-- `preserve` - Preserve field value when removed
-- `tooltip` - Tooltip configuration
-- `extra` - Extra content below the field
-- `hasFeedback` - Show validation feedback icon
-- And all other [Form.Item props](https://ant.design/components/form#formitem)
-
-## API Changes
-
-### No API Changes Required
-
-Since `Form.Item` has no deprecated props in Ant Design v6, no API changes are required. All existing code using CapFormItem will continue to work without modifications.
-
-```tsx
-// All of these continue to work exactly as before
-<CapFormItem label="Username" name="username" required>
-  <CapInput />
-</CapFormItem>
-
-<CapFormItem 
-  label="Email" 
-  name="email" 
-  rules={[{ type: 'email', required: true }]}
-  help="Enter your email address"
->
-  <CapInput type="email" />
-</CapFormItem>
-
-<CapFormItem 
-  label="Password" 
-  name="password" 
-  validateStatus="error"
-  help="Password must be at least 8 characters"
->
-  <CapInput type="password" />
-</CapFormItem>
-```
-
-## Migration Steps
-
-### 1. Update Import
-
-```tsx
-// Before (cap-ui-library)
-import CapFormItem from '@capillarytech/cap-ui-library/CapFormItem';
-
-// After (blaze-ui)
-import { CapFormItem } from '@capillarytech/blaze-ui';
-// or
-import CapFormItem from '@capillarytech/blaze-ui/CapFormItem';
-```
-
-### 2. No Prop Changes Required
-
-Since there are no deprecated props, no prop changes are needed. All existing code will continue to work.
-
-### 3. TypeScript Support (New Benefit)
-
-If using TypeScript, you now get full type checking:
-
-```tsx
-import { CapFormItem } from '@capillarytech/blaze-ui';
-import type { CapFormItemProps } from '@capillarytech/blaze-ui/CapFormItem';
-
-// Type-safe props
-const props: CapFormItemProps = {
-  label: 'Username',
-  name: 'username',
-  required: true,
-  help: 'Enter your username',
-  validateStatus: 'success',
-};
-```
-
-## Examples
-
-### Basic Usage
-
-```tsx
-import { CapFormItem, CapInput } from '@capillarytech/blaze-ui';
-
-function App() {
-  return (
-    <CapFormItem label="Username" name="username">
-      <CapInput placeholder="Enter username" />
-    </CapFormItem>
-  );
-}
-```
-
-### Required Field
-
-```tsx
-import { CapFormItem, CapInput } from '@capillarytech/blaze-ui';
-
-function App() {
-  return (
-    <CapFormItem label="Email" name="email" required>
-      <CapInput type="email" placeholder="Enter email" />
-    </CapFormItem>
-  );
-}
-```
-
-### With Validation Rules
-
-```tsx
-import { CapFormItem, CapInput } from '@capillarytech/blaze-ui';
-
-function App() {
-  return (
-    <CapFormItem 
-      label="Password" 
-      name="password"
-      rules={[
-        { required: true, message: 'Please input your password!' },
-        { min: 8, message: 'Password must be at least 8 characters' }
-      ]}
-    >
-      <CapInput type="password" placeholder="Enter password" />
-    </CapFormItem>
-  );
-}
-```
-
-### With Help Text
-
-```tsx
-import { CapFormItem, CapInput } from '@capillarytech/blaze-ui';
-
-function App() {
-  return (
-    <CapFormItem 
-      label="Email" 
-      name="email"
-      help="We will never share your email with anyone"
-    >
-      <CapInput type="email" placeholder="Enter email" />
-    </CapFormItem>
-  );
-}
-```
-
-### With Validation Status
-
-```tsx
-import { CapFormItem, CapInput } from '@capillarytech/blaze-ui';
-import { useState } from 'react';
-
-function App() {
-  const [status, setStatus] = useState<'success' | 'error' | undefined>();
-
-  return (
-    <CapFormItem 
-      label="Username" 
-      name="username"
-      validateStatus={status}
-      help={status === 'error' ? 'Username is already taken' : undefined}
-    >
-      <CapInput 
-        placeholder="Enter username"
-        onChange={() => setStatus(undefined)}
-      />
-    </CapFormItem>
-  );
-}
-```
-
-### With Form Context
-
-```tsx
-import { CapForm, CapFormItem, CapInput, CapButton } from '@capillarytech/blaze-ui';
-import { Form } from 'antd-v5';
-
-function App() {
-  const [form] = Form.useForm();
-
-  const onFinish = (values: any) => {
-    console.log('Form values:', values);
-  };
-
-  return (
-    <CapForm form={form} onFinish={onFinish}>
-      <CapFormItem 
-        label="Username" 
-        name="username"
-        rules={[{ required: true, message: 'Please input your username!' }]}
-      >
-        <CapInput />
-      </CapFormItem>
-      
-      <CapFormItem 
-        label="Email" 
-        name="email"
-        rules={[
-          { required: true, message: 'Please input your email!' },
-          { type: 'email', message: 'Please enter a valid email!' }
-        ]}
-      >
-        <CapInput />
-      </CapFormItem>
-      
-      <CapFormItem>
-        <CapButton type="primary" htmlType="submit">
-          Submit
-        </CapButton>
-      </CapFormItem>
-    </CapForm>
-  );
-}
-```
-
-## TypeScript Types
-
-```typescript
-import type { FormItemProps } from 'antd-v5';
-
-export interface CapFormItemProps extends FormItemProps {
-  className?: string;
-  children?: React.ReactNode;
-  label?: string;
-  required?: boolean;
-  help?: string;
-  validateStatus?: 'success' | 'warning' | 'error' | 'validating';
-}
-```
-
-## Notes
-
-- The component uses SCSS modules for styling to avoid style conflicts
-- The component uses Ant Design v6 APIs internally (via `antd-v5` package alias)
-- All Form.Item props from Ant Design v6 are supported
-- No deprecated props need to be handled since Form.Item has none in v6
-- The component maintains full backward compatibility with cap-ui-library v8.x
-
-## Verification Results
-
-### Ant Design Component Props Verification
-
-✅ **Form.Item Component**: No deprecated props found
-- Component uses: `Form.Item` from `antd-v5` (Ant Design v6)
-- Deprecated props check: **None** - Form.Item has no deprecated props in v6
-- Migration guide reference: [Ant Design v6 Migration Guide](https://ant.design/docs/react/migration-v6)
-
-### Backward Compatibility
-
-✅ **Full backward compatibility maintained**
-- All props from original component continue to work
-- No prop mapping required
-- No console warnings needed
-
-### Documentation Status
-
-✅ **Documentation complete**
-- README.md created with proper format
-- Deprecated props section documented (none found)
-- Migration examples provided
-- TypeScript types documented

package/CapFormItem/Status.md

@@ -1,73 +0,0 @@
-# Migration Status: CapFormItem
-
-**Last Updated**: 2026-01-31 19:20:17
-
-## Migration Steps
-
-- [x] **Step 0**: Setup branch and remote tracking
-- [x] **Step 1**: Migration Prompt 1 (Main migration)
-- [x] **Step 1.5**: Export component in blaze-ui/components/index.ts
-- [x] **Step 2**: Migration Prompt 2 (Storybook support)
-- [x] **Step 2.5**: Verify deprecated props and prop changes (REQUIRED - enforced)
-- [x] **Step 3**: Migration Prompt 3 (Unit tests)
-- [x] **Step 4**: Migration Prompt 4 (Visual test cases)
-- [x] **Step 5**: Linting (ESLint)
-- [x] **Step 6**: Pre-build Validation
-- [] **Step 7**: Build blaze-ui
-- [] **Step 8**: Visual Testing
-- [] **Step 9**: CSS Analysis (if mismatches found)
-- [] **Step 9.5**: CSS Analysis Completed
-- [] **Step 10**: Git Commit & Push to branch (pre-commit hook will run tests)
-- [] **Step 11**: Create Pull Request
-
-## Deprecated Props Verification
-
-✅ **Verification Complete** - 2026-01-31
-
-### Ant Design Component Used
-- **Form.Item** from `antd-v5` (Ant Design v6)
-
-### Deprecated Props Status
-✅ **No deprecated props found**
-
-The `Form.Item` component from Ant Design v6 does **not** have any deprecated props according to the [Ant Design v6 Migration Guide](https://ant.design/docs/react/migration-v6). 
-
-**Verification Results:**
-- ✅ Component uses: `Form.Item` from Ant Design v6
-- ✅ Deprecated props check: **None** - Form.Item has no deprecated props in v6
-- ✅ Migration guide reference: ANTD_V6_MIGRATION.md reviewed
-- ✅ Documentation: README.md created with proper format
-- ✅ Backward compatibility: Full compatibility maintained (no prop changes needed)
-
-### Documentation
-- ✅ README.md created with "Deprecated Props" section
-- ✅ Documented that Form.Item has no deprecated props
-- ✅ Migration examples provided
-- ✅ TypeScript types documented
-
-**Note**: Step 2.5 is REQUIRED and enforced. 
-- Focus: **Ant Design component prop changes** (e.g., Dropdown, Input, Alert, Tooltip, etc.)
-- Reference: MIGRATION_CHANGELOG_TEMPLATE.md for format, ANTD_V6_MIGRATION.md for Ant Design deprecated APIs
-- Skip: If original component doesn't exist in cap-ui-library
-- All deprecated Ant Design props and prop changes must be documented before proceeding.
-
-## Visual Testing Results
-
-**Last Test**: 2026-01-31 19:20:17
-**Maximum Mismatch**: 0%
-
-### Mismatched Variants:
-- 
-
-
-## CSS Fixes Applied
-
-**Date**: 2026-01-31 10:13:25
-**Summary**: CSS fixes applied based on visual testing analysis.
-
-_See full analysis in: `/Users/sarahkhader/repos/migration/blaze-ui/tools/visual-testing/report/CapFormItem/css-fix-analysis.md`_
-
-
-## Notes
-
-_No notes yet._

package/CapFormItem/tests/USE_CASES_ANALYSIS.md

@@ -1,84 +0,0 @@
-# CapFormItem Use Cases Analysis
-
-## Component Overview
-CapFormItem is a wrapper around Ant Design v6 Form.Item component that:
-- Adds a wrapper div with `cap-form-item-wrapper` class
-- Applies custom className `cap-form-item-v2`
-- Converts children to array using `React.Children.toArray()`
-- Extends all FormItemProps from antd-v5 (Ant Design v6)
-
-## Use Cases NOT Currently Fulfilled
-
-### 1. Custom Validation Logic
-**Status**: ✅ Supported via antd Form.Item `rules` prop
-**Note**: Component passes through all FormItemProps, so validation rules are fully supported through the underlying Form.Item.
-
-### 2. Dependent Field Validation
-**Status**: ✅ Supported via antd Form.Item `dependencies` prop
-**Note**: Since component extends FormItemProps, `dependencies` prop is available.
-
-### 3. Custom Error Message Formatting
-**Status**: ⚠️ Limited
-**Current Behavior**:
-- Error messages come from Form.Item validation rules
-- `help` prop displays static help text
-- No custom error message formatting or styling
-
-**Potential Gap**: If custom error message formatting/styling is required, it would need to be added.
-
-### 4. Conditional Rendering Based on Form Values
-**Status**: ✅ Supported via antd Form.Item `shouldUpdate` or `noStyle` props
-**Note**: Component passes through all props, so conditional rendering is supported.
-
-### 5. Custom Label Rendering
-**Status**: ⚠️ Basic support
-**Current Behavior**:
-- `label` prop accepts string
-- FormItemProps supports ReactNode for label, but component interface only shows string
-
-**Potential Gap**: While FormItemProps supports ReactNode labels, the TypeScript interface only explicitly shows `label?: string`. This works due to prop spreading, but the type definition could be more explicit.
-
-### 6. Tooltip Integration
-**Status**: ✅ Supported via antd Form.Item `tooltip` prop
-**Note**: Component extends FormItemProps which includes `tooltip` prop.
-
-### 7. Extra Information Display
-**Status**: ✅ Supported via antd Form.Item `extra` prop
-**Note**: Component extends FormItemProps which includes `extra` prop.
-
-### 8. Custom Help Text Rendering
-**Status**: ✅ Supported
-**Current Behavior**:
-- `help` prop displays help text
-- Form.Item also supports `help` prop natively
-
-**Note**: Both custom `help` prop and Form.Item's native `help` prop work, but they may conflict if both are provided.
-
-### 9. Children Array Handling
-**Status**: ⚠️ Potential Issue
-**Current Behavior**:
-- Uses `React.Children.toArray(children)` which converts children to array
-- This may affect how single children are rendered
-
-**Potential Gap**: If a single child is passed, it's converted to an array. This should work fine with Form.Item, but could affect edge cases.
-
-### 10. Form Layout Integration
-**Status**: ✅ Supported
-**Note**: Component works within Form context and respects Form's layout prop (vertical/horizontal/inline).
-
-## Recommendations
-
-1. **Type Safety**: Consider explicitly typing `label` as `React.ReactNode` instead of just `string` to match FormItemProps capabilities.
-
-2. **Help Prop**: Document that both custom `help` prop and Form.Item's native `help` prop exist and may conflict.
-
-3. **Children Handling**: Document that children are converted to array, which should be transparent but worth noting.
-
-4. **Validation**: Component relies entirely on antd Form.Item validation. No custom validation logic is added.
-
-## Conclusion
-
-The component is a thin wrapper that successfully passes through all Form.Item functionality. Most use cases are fulfilled through the underlying Form.Item component. The main considerations are:
-- Type definitions could be more explicit for ReactNode props
-- Children array conversion is transparent but worth documenting
-- No custom validation or error handling logic beyond what Form.Item provides

package/CapGraph/README.md

@@ -1,69 +0,0 @@
-# CapGraph – Migration (Antd v3→v6) Step 1
-
-## Stage 1: Pre-Analysis Report
-
-### Analysis Report for CapGraph
-
-#### 1. Antd Style Overrides Found
-
-| Line # | Old Override | Can Tokenize? | Token Path | Token Value | Override Reason |
-|--------|-------------|---------------|------------|-------------|-----------------|
-| N/A    | None        | N/A           | N/A        | N/A         | Component uses BizCharts (G2), not Ant Design |
-
-**Tokenizable overrides**: 0  
-**Non-tokenizable overrides**: 0  
-**No antd overrides found – theme config update skipped.**
-
-`styles.scss` contains only `@import '../styles/_variables.scss'` and a wrapper class. No `:global` or `.ant-` usage.
-
-#### 2. API Breaking Changes
-
-| Old API | New API | Affected Props |
-|---------|---------|----------------|
-| N/A     | N/A     | CapGraph does not wrap an Ant Design component |
-
-#### 3. Backward Compatibility Plan
-
-| Deprecated Prop | Fallback Logic |
-|-----------------|----------------|
-| None            | N/A – no deprecated props in this migration |
-
-#### 4. Type Definitions Needed
-
-- `CapGraphProps` – main component props
-- `CapGraphLegendConfig` – legend marker, position, spread props
-- `CapGraphGuideItem` – guide position, content
-- `CapGraphGeomItem` – graphList item (type, groupBy, colors, shape, tooltip, label, etc.)
-
-#### 5. PropTypes Removal
-
-- [x] Component uses PropTypes: **YES** (removed)
-- [x] PropTypes file exists: **NO**
-- [x] PropTypes imports found: **YES** (removed)
-- [x] Component.propTypes assignments found: **YES** (removed)
-- All prop types moved to `types.ts` (TypeScript interfaces).
-
-#### 6. DefaultProps Removal
-
-- [x] Component uses defaultProps: **YES** (removed)
-- [x] Component.defaultProps assignments found: **YES** (removed)
-- [x] Old function syntax with props parameter: **NO** (was class component; converted to function)
-- [x] Default values assigned inside function body: **NO**
-- Defaults applied via destructuring: `graphList = []`, `xAxisProps = {}`, `yAxisProps = {}`, `title = null`, `y1AxisProps = {}`, `chartProps = {}`.
-
----
-
-## Implementation Summary
-
-- **types.ts**: Added; defines `CapGraphProps`, `CapGraphLegendConfig`, `CapGraphGuideItem`, `CapGraphGeomItem`.
-- **index.tsx**: Converted from class to function component; removed PropTypes and defaultProps; uses TypeScript types; `tooltipIndex` moved to `useState`; defaults in destructuring.
-- **styles.scss**: Uses CSS Modules (`.cap-graph-wrapper`); no `:global` or `.ant-`; variables import retained.
-- **Package dependency**: `bizcharts` added to `package.json` (^3.5.5).
-- **Export**: `CapGraph` and `CapGraphProps` added to `components/index.ts`.
-
-## Validation
-
-- **SCSS**: No `:global` or `.ant-` in `styles.scss`.
-- **Theme config**: Not updated (no Antd component).
-- **PropTypes/defaultProps**: Removed; no remaining references.
-- **TypeScript**: Types in `types.ts`; `bizcharts` declared in `types.d.ts` for module resolution.