Automated tests exercise the library's behavior. The coverage requirement is at least 95.01% independently for statements, branches, functions and lines: executed instructions, decision paths, functions and source lines.
Coverage is not an accessibility score or a guarantee for your application's theme. Compilation, public imports and server-rendered interactions are checked separately. Your application still needs the task checks below.
Build the application and verify its real task flows: editable models, validation, disabled and loading state, keyboard navigation and focus restoration. Repeat on supported browsers and representative narrow and wide layouts.
For server-rendered applications, inspect useful initial HTML and exercise the UI after hydration. Check translated routes, title and description metadata, and browser console errors as part of the same release review.
Import each component from its documented public package path, such as @neural-ui/core/button. Avoid paths into the library's source or private folders: those files are not a supported API and can change without a public contract.
A bundle is the JavaScript your application sends to the browser. Importing only the components and icon definitions you use lets the build remove unused code. Measure the production build of your own application; a library's size alone does not predict a page's download size.
Also check TypeScript's strict compilation. A working browser build does not by itself prove that every published type declaration resolves correctly in every supported tool.
