Verification and limitations
Current package availability, supported checks and accessibility limitations.
Current release status
The Faye UI npm package is unpublished and not ready for release. The 0.1.0 publication was withdrawn on October 23, 2026. The final npm package metadata and support destinations still require review. The guides describe the implemented API; they do not establish npm availability or certification.
What release qualification covers
Each release candidate is checked as an installed npm package as well as in the development workspace. Checks cover types and imports, generated tokens and styles, React behavior, keyboard navigation and focus, forms, overlays, themes, motion, and cleanup. Chromium, Firefox and WebKit exercise the component suite. Production documentation and consumer applications are also tested.
Server rendering, streaming, React Server Components and client rendering have separate integration checks. Package checks verify declarations, explicit entrypoints, stylesheet delivery, dependency boundaries and installed application builds. Dependency auditing is part of qualification.
Visual and interaction review
Rendered examples are inspected in light and dark themes, narrow layouts, enlarged text and right-to-left layouts. Reviews include open menus and dialogs, loading and error states, pointer and keyboard reactions, animations, reduced motion and forced colors. A component appearing in the gallery is not sufficient evidence that all its interactions work.
Checks run against a fixed candidate. Changes require fresh qualification; a successful older run does not qualify a newer package. Release checks are tied to the exact package being reviewed. Repository access is not needed to install or use a published release. See installation for npm publication status.
Accessibility and review limits
Semantic labels, descriptions, validation errors and keyboard operation remain available continuously. Automated accessibility checks, keyboard/focus flows, zoom and reflow, reduced motion and forced colors are part of qualification. See accessibility for system preferences and optional interaction guidance.
Physical-device and assistive-technology certification, and qualified linguistic review of the optional language catalogs, have not been performed. Those reviews remain unperformed. Automated tests and rendered-image inspection do not replace those reviews.
Supported boundaries
The package includes UI primitives, controls and compositions. Specialized data-grid, chart, advanced date/time, rich-text and virtualization engines remain separate extensions. Native-column Masonry and measured PackedMasonry have different layout contracts; the latter starts with a server-rendered grid fallback.
Portable customization, DTCG exchange and design-tool adapters have documented bounds. Design-tool host integration has separate limitations and is not required to build applications. Publishing the npm package and deploying the documentation site are separate operations.