@epam/ai-dial-ui-kit

中文文档
0.16.3发布于 2026/11/16Apache-2.0TypeScriptESM + CJS构建来源已验证近 30 天下载 4.4万

A modern UI kit for building AI DIAL interfaces with React

原始使用文档
文档目录29 节
  1. Table of Contents
  2. ✨ Highlights
  3. 📖 Documentation
  4. 🚀 Quick Start
  5. Prerequisites
  6. Installation
  7. Basic Usage
  8. Optional: Markdown Components CSS
  9. Development
  10. Controlled dropdown menus
  11. Prerequisites
  12. Development Setup
  13. Running Tests
  14. Project Structure
  15. 🎨 Theming & Customization
  16. Public class names
  17. ♿ Accessibility
  18. Naming icon-only controls
  19. Target size (WCAG 2.5.5, Level AAA)
  20. 📖 Storybook
  21. Stories
  22. Documents
  23. 🚀 Usage in Projects
  24. Tree Shaking
  25. 🤖 AI Agent MCP Server
  26. 🤝 Contributing
  27. 🔒 Security
  28. 📄 License
  29. 🌟 Related Projects

AI DIAL UI Kit

AI-DIAL-UI-KIT project logo

The AI DIAL UI Kit is an production-ready React component library designed to streamline your development process. It features a collection of base components, such as Buttons, Inputs, Dropdowns, and more — allowing you to effortlessly reuse elements, quick and easy.

npm version License: Apache 2.0 TypeScript React

Table of Contents

✨ Highlights

  • 🎨 Unified User Experience: Ui Kit usage helps with design consistency across AI DIAL applications
  • ⚡ Modern Stack: Built with latest React, TypeScript, Vite, and Tailwind CSS
  • 🎨 Highly Customizable: Deep theming capabilities with CSS custom properties
  • 🧪 Well-Tested: Comprehensive test coverage (70%+) with Vitest and React Testing Library
  • 📚 Storybook Ready: Includes interactive component documentation and development playground
  • 🛠️ Developer Experience: Leverage ESLint and Prettier for maintainable code quality
  • 📦 Distribution Ready: Deployed as NPM package ready for easy integration

📖 Documentation

Explore our components and their usage in our interactive Storybook documentation.

🚀 Quick Start

Prerequisites

  • Node.js >= 22.2.0
  • npm >= 10.7.0

Installation

npm install @epam/ai-dial-ui-kit

Basic Usage

import { DialPrimaryButton } from '@epam/ai-dial-ui-kit';
import '@epam/ai-dial-ui-kit/styles.css';

function App() {
  return (
    <div>
      <DialPrimaryButton onClick={() => alert('Hello AI DIAL!')} />
    </div>
  );
}

Optional: Markdown Components CSS

If you're using the MarkdownEditor (loaded through LazyMarkdownEditor), you need to import the required CSS files globally in your application (e.g., in your root layout or main entry point):

import '@uiw/react-markdown-preview/markdown.css';
import '@uiw/react-md-editor/markdown-editor.css';

This ensures the CSS is loaded once per application rather than being bundled with each component instance, reducing bundle size.

Development

Controlled dropdown menus

ButtonDropdown accepts controlled open / onOpenChange or an uncontrolled defaultOpen. Its dropdownProps forwards search, placement and menu sizing options to Dropdown. Set iconAfter={null} for an icon-only trigger; otherwise the default chevron follows the effective open state.

DropdownItem.subMenuOpen and onSubMenuOpenChange let a host retain the active submenu across presentation changes. Omitting them preserves the default uncontrolled behavior. An already-open submenu restores focus on mount, and the kit owns arrow navigation, RTL placement, Escape and focus return. renderSubMenu can provide custom content without placeholder children. Leaf items forward iconAfter as trailing content alongside the existing disabled/danger states.

Prerequisites

  • Node.js >= 22.2.0
  • npm >= 10.7.0
  • Git

Development Setup

  1. Clone the repo

    git clone https://github.com/epam/ai-dial-ui-kit.git
    cd ai-dial-ui-kit
    
  2. Install Dependencies

    npm install
    
  3. Start Development Environment

    # Start Storybook for component development
    npm run storybook
    
    # Run tests in watch mode
    npm run test -- --watch
    
    # Start Vite dev server
    npm run dev
    

Running Tests

# Run all tests with coverage
npm run test

Project Structure

src/
├── components/          # React components
│   ├── Button/         # Example component
│   │   ├── Button.tsx
│   │   ├── Button.spec.tsx
│   │   └── Button.stories.tsx
│   └── ...
├── styles/             # Global styles and Tailwind configuration
│   ├── buttons.scss
│   ├── typography.scss
│   └── tailwind-entry.scss
├── types/              # TypeScript type definitions
└── index.ts            # Main entry point

🎨 Theming & Customization

The library uses CSS custom properties for comprehensive theming. Override these variables to match your brand:

:root {
  /* Background layers */
  --bg-layer-0: #000000;
  --bg-layer-1: #0C101D;
  --bg-layer-2: #171B21;
  
  /* Text colors */
  --text-primary: ##EEF1F7;
  --text-secondary: #9CA3AF;
  --text-tertiary: #6B7280;
   ...
}

Full list of variables is available here

Corner radii of the 2.0 controls are themable the same way. Each defaults to the fully rounded pill the buttons ship with, so setting nothing keeps the stock look:

:root {
  --radius-control: 12px; /* Button at standard and large size */
  --radius-control-small: 8px; /* Button at ElementSize.Small */
  --radius-control-icon: 9999px; /* IconButton, ToggleIconButton — any size */
}

Labelled and icon-only buttons read separate variables on purpose: a design that wants squarer action buttons usually still wants its icon buttons round.

These are defaults, not overrides: a rounded-* utility passed to a single control through className still wins, because a consumer's utilities are emitted after this package's stylesheet.

Overlay stacking

Overlays render in a portal at the end of <body>, so they stack against the host's own fixed and sticky chrome — a header, a side sheet, an embedding overlay. They sit on a four-step ladder driven by one variable:

LayerUtilityz-indexComponents
Popupz-popupvar(--z-overlay, 52)Popup backdrop, both generations
Floating panelz-floating--z-overlay + 1Dropdown and Select overlays, submenus, Calendar
Interactive panelz-interactive-tooltip--z-overlay + 2InteractiveTooltip
Tooltipz-tooltip--z-overlay + 3Tooltip, both generations

To lift every overlay above a host layer, set the base once:

:root {
  --z-overlay: 1000; /* popup 1000, dropdown 1001, interactive tooltip 1002, tooltip 1003 */
}

Each layer is a fixed step above the one below, so raising the base never reorders them: a dropdown still opens above the popup it sits in, and a tooltip above the dropdown row that triggered it. Set the variable on :root, or in the class a ThemeScope re-applies to its portalled overlays — a portal escapes any other wrapper, so a value set only there never reaches the overlay.

A single overlay can still be moved on its own: a z-* utility passed to a Dropdown's listClassName, a Popup's overlayClassName, an InteractiveTooltip's contentClassName or a Calendar's panelClassName replaces the layer's own step rather than landing beside it, because mergeClasses knows the ladder utilities are z-index.

Public class names

Some hosts need to restyle a part of a component the props do not reach — the padding of a menu's row list, the radius of a row, the caret badge of an icon trigger. The kit's own classes are Tailwind utilities and hashed module locals, so a host that reaches for them ends up on selectors that break on the next upgrade: [class*='_selectedItem_'], > div:nth-child(2) > button, [role='none'][aria-label='dropdown'] — the last of which is an accessibility contract and, being a plain English string, is not one a localised host can rely on either.

Every design-system 2.0 component therefore stamps a stable class on the element that draws it. They are exported as one record:

import { DIAL_KIT_CLASS } from '@epam/ai-dial-ui-kit';

DIAL_KIT_CLASS.menuItem; // 'dial-kit-menuitem'
.dial-kit-dropdown-list {
  padding-block: 0;
}

.dial-kit-menuitem {
  border-radius: 8px;
}

Nothing in dist/index.css selects on them: they carry no declarations of their own and exist only as selectors, so a host's rule needs no !important it would not otherwise need. Renaming one, or moving it to a different element, is a breaking change and goes through the migration-guide process.

Feedback and status

KeyClassElement
spinnerdial-kit-spinnerThe role="status" root of a Spinner
progressBardial-kit-progress-barThe outermost element of a ProgressBar — its wrapper, or the track when it has neither label nor readout
skeletondial-kit-skeletonThe root of a Skeleton
notificationdial-kit-notificationThe Notification surface, including every toast and section-message wrapper
noDataContentdial-kit-no-data-contentThe empty-state root of NoDataContent
loginScreendial-kit-login-screenThe section root of a LoginScreen
stateScreendial-kit-state-screenThe section root of a StateScreen
liveRegiondial-kit-live-regionThe always-mounted wrapper of a LiveRegion, or of an announced CaptionText / ErrorText
transferQueuedial-kit-transfer-queueThe role="status" panel of a TransferQueue: header, rows and aggregate bar

Text

KeyClassElement
highlightdial-kit-highlightThe text element of a Highlight
captionTextdial-kit-caption-textThe caption line under a field
errorTextdial-kit-error-textA caption in its error variant, additive to captionText
labeldial-kit-labelThe Label root, wrapping its label element and its info button
labelledTextdial-kit-labelled-textThe root of a LabelledText, wrapping its caption and value

Containers

KeyClassElement
stepsdial-kit-stepsThe ol root of a Steps
cardShelldial-kit-card-shellThe article element of a CardShell
analyticsCarddial-kit-analytics-cardThe root of an AnalyticsCard
analyticsBardial-kit-analytics-barThe root of an AnalyticsBar, stacked or inline
analyticsBarGroupdial-kit-analytics-bar-groupThe root of an AnalyticsBarGroup, which is its accordion
analyticsHistogramdial-kit-analytics-histogramThe root of an AnalyticsHistogram
collapsibleSidebardial-kit-collapsible-sidebarThe aside element of a CollapsibleSidebar
resizableContainerdial-kit-resizable-containerThe content box inside a ResizableContainer's resize frame
resizeHandledial-kit-resize-handleThe role="separator" element of a ResizeHandle
popupdial-kit-popupThe role="dialog" panel of a Popup
bottomSheetdial-kit-bottom-sheetThe role="dialog" panel of a BottomSheet
bottomSheetOverlaydial-kit-bottom-sheet-overlayThe backdrop of a BottomSheet, which holds the panel
sideDrawerdial-kit-side-drawerThe role="dialog" panel of a SideDrawer, open or closed
confirmationPopupdial-kit-confirmation-popupA ConfirmationPopup's panel, additive to popup
accordiondial-kit-accordionThe root of an Accordion
folderPathdial-kit-folder-pathThe breadcrumb root of a FolderPath
breadcrumbsdial-kit-breadcrumbsThe nav element of a Breadcrumbs trail
breadcrumbsItemdial-kit-breadcrumbs-itemOne segment of it: the link, button or span that draws the label

Menus and overlays

KeyClassElement
dropdowndial-kit-dropdownThe trigger wrapper of a Dropdown
dropdownListdial-kit-dropdown-listThe role="none" item list inside a dropdown overlay, and a submenu's own list. Both generations
dropdownSearchdial-kit-dropdown-searchThe search row above the item list of a searchable Dropdown
menuItemdial-kit-menuitemOne overlay row: a dropdown item, a Select option, a submenu trigger or child
menuItemCheckdial-kit-menuitem-checkThe trailing check of a chosen MenuItemMark.Check row
tooltipdial-kit-tooltipThe bubble of a Tooltip
interactiveTooltipdial-kit-interactive-tooltipThe panel of an InteractiveTooltip
ellipsisTooltipdial-kit-ellipsis-tooltipThe text element of an EllipsisTooltip, which is also its trigger

Fields

KeyClassElement
searchdial-kit-searchThe Search field box, additive to dial-kit-input
passwordInputdial-kit-password-inputThe PasswordInput field box, additive to dial-kit-input
numberInputdial-kit-number-inputThe NumberInput field box, additive to dial-kit-input
tagInputdial-kit-tag-inputThe TagInput field box, additive to dial-kit-input
autocompleteTagInputdial-kit-autocomplete-tag-inputThe AutocompleteTagInput field box, additive to dial-kit-input
selectdial-kit-selectThe root of a Select
inlineSelectdial-kit-inline-selectThe trigger button of an InlineSelect
calendardial-kit-calendarThe root of a Calendar, in every mode
schemaRendererdial-kit-schema-rendererThe root of a SchemaRenderer
schemaRendererSectiondial-kit-schema-renderer-sectionOne collapsible SchemaRenderer section card, at any depth
fileDropzonedial-kit-file-dropzoneThe drop area of a FileDropzone
fileIcondial-kit-file-iconThe root of a FileIcon: glyph or spinner, and the shared badge
fileNamedial-kit-file-nameThe row of a FileName: its type icon, the name and any details
folderNamedial-kit-folder-nameThe FileName row of a FolderName, additive to fileName
sharedEntityIndicatordial-kit-shared-entity-indicatorThe badge of a SharedEntityIndicator, including the one on a FileIcon
badgedial-kit-badgeThe root of a Badge: the label box, with its icon when it has one
avatardial-kit-avatarThe root of an Avatar: the image, or the initials box that replaces it
entityIdentitydial-kit-entity-identityThe root row of an EntityIdentity: icon, type label, name and version
selectedEntityCarddial-kit-selected-entity-cardThe bordered card of a SelectedEntityCard, not the wrapper that also holds its error
formSectiondial-kit-form-sectionThe section root of a FormSection: heading row, description and content
radioGroupPopupFielddial-kit-radio-group-popup-fieldThe root of a RadioGroupPopupField

Controls

KeyClassElement
switchdial-kit-switchThe row of a Switch: the control and its label
checkboxdial-kit-checkboxThe row of a Checkbox
checkboxBoxdial-kit-checkbox-boxThe decorative box a CheckboxBox draws
radiodial-kit-radioThe row of a Radio
radioGroupdial-kit-radio-groupThe root of a RadioGroup
segmentedControldial-kit-segmented-controlThe role="radiogroup" track of a SegmentedControl
segmentedControlItemdial-kit-segmented-control-itemOne segment of it
tabsdial-kit-tabsThe outermost element of a Tabs — the heading wrapper, or the tab list when there is no sectionLabel
tabListdial-kit-tab-listThe role="tablist" inside it, in either orientation
tabdial-kit-tabOne tab inside it
tabSelecteddial-kit-tab-selectedThe selected tab, in either orientation
tabsSectionLabeldial-kit-tabs-section-labelThe sectionLabel heading above a Tabs
tagdial-kit-tagA Tag pill, including a TagInput's rows
filterChipsdial-kit-filter-chipsThe role="group" row of a FilterChips; its chips carry dial-kit-tag
toggleIconButtondial-kit-toggle-icon-buttonA ToggleIconButton, additive to dial-kit-base-icon-button
toggleChipdial-kit-toggle-chipThe <button aria-pressed> of a ToggleChip
closeButtondial-kit-close-buttonA CloseButton, additive to dial-kit-base-icon-button
infoButtondial-kit-info-buttonAn InfoButton, additive to dial-kit-base-icon-button
buttonDropdowndial-kit-button-dropdownThe wrapper of a ButtonDropdown

Components with no entry, and why

Some 2.0 components are deliberately absent, because the element a host would target already carries a stable class:

ComponentTarget it already
Button and its six variant wrappersdial-kit-base-button (plus a per-variant class such as dial-kit-primary-solid-button)
IconButton and its five variant wrappersdial-kit-base-icon-button
FabButtondial-kit-fab-button
Inputdial-kit-input
Textareadial-kit-textarea
Sliderdial-kit-slider
MarkdownEditordial-kit-markdown-editor
Griddial-kit-grid (exported as GRID_ROOT_CLASS)

Five more contribute no element of their own, and are addressed through what they render: ThemeScope (a display: contents wrapper), MultiSelectTags (Tags), TooltipContainer / TooltipTrigger, and ErrorBoundary (its LiveRegion and fallback StateScreen).

Two neighbouring elements are reached through props instead, and keep being: a Dropdown's floating panel takes listClassName, and a Popup's backdrop takes overlayClassName.

♿ Accessibility

Naming icon-only controls

DialFabButton, DialIconButton, and IconButton render no text, so they need an explicit accessible name. Pass aria-label; if you pass only a string tooltipProps.tooltip, it is used as the label instead. Do not rely on the tooltip alone to convey the name — a tooltip's aria-describedby lands on a wrapper element rather than on the control, and tooltips are suppressed entirely on mobile.

InfoButton names itself from caption for the same reason. Pass a short aria-label when the caption is a full sentence, so the name stays scannable.

Target size (WCAG 2.5.5, Level AAA)

Standard-size buttons render at 40×40 but expose a 44×44 pointer target via the dial-kit-enhanced-target utility, which grows the target with a transparent pseudo-element. The visible control is unchanged, so layouts keep their existing metrics. WCAG 2.5.5 measures the region that accepts a pointer action, not the visible decoration.

A control too small for a 44px target to clear its neighbours uses dial-kit-minimum-target instead, which applies the same pseudo-element at the Level AA minimum of 24×24 (WCAG 2.5.8).

These controls are documented exceptions and meet Level AA (2.5.8, 24×24) but not AAA:

ControlSizeWhy it is excluded
ElementSize.Small variants24×24A 44px target overhangs 10px per side and would overlap adjacent controls in dense toolbars
ButtonAppearance.LinkcontentExempt under the 2.5.5 Inline exception; expanding it would overlap surrounding copy
DialCloseButtonicon-sizedRenders h-auto w-auto, so its target follows the caller's icon size
DialInfoButton, InfoButton24×24Fixed small affordance, same overlap constraint as small variants
Standard 2.0 fields (Input, Select, RadioGroupPopupField)40px tallThe pointer target spans the full field width but stays 4px short of 44 vertically; the height is a shared form design token, not a per-control choice. .dial-kit-input clips its overflow, so the pseudo-element cannot grow the target either
Tag remove button16×16 renderedReaches 24×24 through dial-kit-minimum-target; a 44px target would overhang 14px per side and swallow the neighbouring tags of a TagInput row
Clickable Tag32px tallA 44px target would overhang 6px per side and swallow the neighbouring chips of a filter row; the tag is already wider than 24px on both axes
ToggleChip32px tallSame pill as a clickable Tag: a 44px target would overhang 6px per side and swallow the neighbouring chips of a toggle row; the chip is already wider than 24px on both axes
Radio circle20×20 renderedReaches 24×24 through dial-kit-minimum-target; a 44px target would overhang 12px per side and swallow the adjacent label. Clicking the label selects the radio, so the practical target is wider
Checkbox box20×20 renderedReaches 24×24 through dial-kit-minimum-target; a 44px target would overhang 12px per side and swallow the adjacent label. Clicking the label toggles the checkbox, so the practical target is wider
Slider track row24px tallThe pointer target spans the full track width but is only 24px tall; a 44px row would add 20px of dead space to every form the slider sits in, and the thumb is dragged rather than tapped
Breadcrumbs segment linkcontentExempt under the 2.5.5 Inline exception — a segment is a text link in a line of text, and expanding it would overlap the segments beside it
Breadcrumbs overflow button16×16 renderedReaches 24×24 through dial-kit-minimum-target; a 44px target would overhang 14px per side and swallow the segments on either side of it in an inline trail
SegmentedControl segment32px tallSits 4px from its neighbours inside a 40px track, so a 44px target would overhang 6px per side and swallow the adjacent segments; the segment is already wider than 24px on both axes
ResizeHandle8px wide pointer stripThe handle has to sit exactly on the panel boundary, so a 44px-wide strip would swallow content on both sides of it — essential to the control. It is a focusable separator, so the resize is also available from the keyboard with the arrow keys
ResizableContainer resize handle10px wide pointer stripThe handle has to sit exactly on the panel boundary, so a 44px-wide strip would swallow content on both sides of it — essential to the control. It is a focusable separator, so the resize is also available from the keyboard with the arrow keys

Give small-variant controls at least 20px of surrounding space if you need to reach AAA in a specific layout, or use the standard size instead.

📖 Storybook

Storybook is a handy library for documenting and developing of UI components.

Stories

To run fully interactive storybook:

Development mode

npm run storybook
# Open http://localhost:6006

Production Build

npm run build-storybook

Production start

npx http-server ./storybook-static
# Open http://127.0.0.1:8080/

Documents

To run documents only:

Development mode

npm run storybook-docs
# Open http://localhost:54800/

Production build

npm run build-storybook-docs

Production start

npx http-server ./storybook-static
# Open http://127.0.0.1:8080/

Storybook provides:

  • 📖 Interactive component documentation
  • 🎨 Visual testing playground
  • ♿ Accessibility testing tools
  • 📱 Responsive design testing
  • 🎯 Component isolation

🚀 Usage in Projects

Next.js Integration
  1. Install the package. React is the only peer you have to supply — everything the kit renders with, it installs itself.
npm install @epam/ai-dial-ui-kit
npm install react react-dom

Add the editor package only if you use the Markdown editor (LazyMarkdownEditor). It is an optional peer, so npm install stays quiet without it, and the kit only reaches for it when the editor actually mounts:

npm install @uiw/react-md-editor
  1. Import style in the root layout of the project:
// app/layout.tsx
import "@epam/ai-dial-ui-kit/styles.css";
  1. Usage example
// app/page.tsx
"use client";
import { DialPrimaryButton } from "@epam/ai-dial-ui-kit";

export default function Home() {
  return (
    <div className="w-full h-full flex flex-col gap-3 items-center justify-center">
      <h1>Test library</h1>
      <DialPrimaryButton onClick={() => alert('Hello AI DIAL!')} />
    </div>
  );
}

Tree Shaking

Import only the components you need:

// ✅ Good - Tree shakable imports
import { DialPrimaryButton, DialInput } from '@epam/ai-dial-ui-kit';
import '@epam/ai-dial-ui-kit/styles.css'; // Import styles separately

// ❌ Avoid - Imports entire library
import * as UIKit from '@epam/ai-dial-ui-kit';

🤖 AI Agent MCP Server

The AI DIAL UI Kit includes a built-in MCP (Model Context Protocol) server that enables AI agents to discover components, types, hooks, and utilities programmatically. This allows AI assistants to generate accurate, type-safe component code without hallucination.

Component results are ranked generation 2.0 first — the current design system, exported without the Dial prefix — and each legacy Dial* component points at its 2.0 replacement, so agents land on the right component by default.

For setup, configuration, and detailed resources, see the MCP Server Guide.

🤝 Contributing

We welcome contributions! Please see our Contributing Guide for details on:

  • Code style guidelines
  • Testing requirements
  • Pull request process

🔒 Security

If you discover a security vulnerability, please refer to our Security Policy.

📄 License

Apache 2.0 - see the LICENSE file for details.

  • AI-DIAL - Entrypoint for all AI Dial projects

Made with ❤️ by EPAM Systems

版本与发布记录

@epam/ai-dial-ui-kit 共发布 889 个版本,首次发布于 2025/09/18;过去 12 个月发布了 721 个版本。最新版本附带 npm provenance 构建来源证明,可追溯到公开的 CI 构建记录。

版本发布日期距今
0.16.3latest2026/11/16今天
0.17.0-dev.11development2026/11/16今天
0.17.0-dev.102026/11/142 天前
0.16.22026/11/142 天前
0.17.0-dev.92026/11/142 天前
0.17.0-dev.82026/11/132 天前

其他发布通道:next → 0.9.0-rc.40,release-0.14 → 0.14.3,development → 0.17.0-dev.11。

关于 @epam/ai-dial-ui-kit 的常见问题

@epam/ai-dial-ui-kit 是什么?

A modern UI kit for building AI DIAL interfaces with React

如何安装 @epam/ai-dial-ui-kit?

在项目目录运行 npm install @epam/ai-dial-ui-kit,或使用 pnpm add / yarn add / bun add。它还需要宿主项目提供 peer 依赖:react(^19.2.5)、react-dom(^19.2.5)。npm 7 及以上与 pnpm 8 及以上默认会自动安装必需的 peer 依赖,Yarn 需要手动安装。它还提供命令行工具 ai-dial-ui-kit-mcp,可以用 npx ai-dial-ui-kit-mcp 直接运行。

@epam/ai-dial-ui-kit 支持 TypeScript 吗?

支持。包内自带 TypeScript 类型声明(package.json 声明了 types 入口),安装后即可获得类型提示,无需再安装 @types 包。

@epam/ai-dial-ui-kit 支持 ESM 还是 CommonJS?

同时提供 ES Module 与 CommonJS 入口,import 和 require() 都可以使用,打包工具会自动选择合适的版本。

@epam/ai-dial-ui-kit 需要什么版本的 Node.js?

package.json 的 engines 字段要求 Node.js >=22.2.0。版本不符时 npm 默认只给出警告,开启 engine-strict 后会拒绝安装。

@epam/ai-dial-ui-kit 可以商用吗?

@epam/ai-dial-ui-kit 使用 Apache-2.0 许可。宽松许可:允许商业使用、修改和再分发,并附带明确的专利授权;分发时需保留许可与 NOTICE 文件,修改过的文件要注明改动。以上为概括,不构成法律意见,请以许可原文为准。

@epam/ai-dial-ui-kit 的下载量有多少?

根据 npm 官方下载统计,@epam/ai-dial-ui-kit 在 2026/10/14 – 2026/11/12 这 30 天内被下载 44,466 次,日均约 1,482 次。下载量会把 CI 构建、镜像同步和作为其他包依赖的安装一并计入,适合横向比较热度,不能直接等同于使用人数。

@epam/ai-dial-ui-kit 还在维护吗?

最新版本 0.16.3 发布于 2026/11/16(今天);至今共发布 889 个版本,其中过去 12 个月发布了 721 个;首次发布于 2025/09/18。发布频率只是参考信号:功能稳定的工具可能很少需要更新,建议结合源码仓库的 issue 和提交记录判断。