Skip to content
nexus-dialogs
GitHub npm

Limitations

What nexus-dialogs does not do, which browsers it is tested with, how it is versioned and how much of the code the tests cover. The best thing about a library you want to use seriously is that it says clearly how far it goes.

#In one sentence

nexus-dialogs is a library of transactional interfaces for business applications: the part of your system where someone confirms, captures, approves, imports or corrects data. It is not a design system, nor a state manager, nor a full data table.

#Known limitations

#Guarantees by module

From 1.0, every module follows semantic versioning: only a major version breaks (see Versions). This table says how settled each module is and which limitation conditions it, not that it has been validated by external users (see above: there are no public production cases yet).

ModuleStatusSinceMain limitation
nexus-dialogs (core)Stable0.1.0Dialogs stack, they are not queued; browser only
formsStable0.1.0Drafts in localStorage; file upload cannot be cancelled
toastStable0.1.0A single queue and a single position
themesStable0.1.0Customized with --nd-* variables, not with your CSS (Shadow DOM)
patternsStable0.1.0Texts in Spanish and English; more languages with labels
mxStable0.1.0The RFC does not compute the homoclave and nothing queries SAT, IMSS or banks
vueMaturing0.3.0Vue 3.3 or later
reactMaturing0.4.0React 18 or later
angularMaturing0.3.0ESM only and Angular 16 or later
swalPartial0.3.0Compatible on purpose only in part: see the matrix. html comes out as text by default
import (import and export)Maturing0.4.0Excel only the basics; the export has not been opened in Microsoft Excel, only in LibreOffice
tableMaturing0.4.0Choosing rows; not a full data table
rrhhMaturing0.4.0JSON templates that you adapt to your rules; you must provide the resolvers
sepomexMaturing0.4.0You publish the catalog's JSON files
tabsMaturing0.5.0New: tabs with content as text, node or function
timelineMaturing0.5.0New: step-by-step tracking

Accessibility has its own note: there are automated tests, but screen readers are pending manual validation (see Accessibility).

#Browsers

BrowserMinimumTests
Chrome / Edge111Current Chromium on every change
Firefox113Current Firefox on every change (axe does not run in Firefox because of a tool limitation)
Safari16.4Current WebKit on every change

The minimums come from the modal <dialog>, color-mix() and constructable stylesheets; without the latter a fallback <style> is used (with a strict CSP, it needs configure({ nonce })). Old versions are not tested separately. There is no support for Internet Explorer. Which feature requires which version and the support policy: Support.

#Versions and breaking changes

The library follows SemVer:

#Test coverage

Coverage of the unit tests (Vitest, measured in the latest review): lines 90%, statements 88%, functions 87%, branches 79%. CI fails if it drops below the thresholds (89 / 86 / 85 / 76). On top of that come the real-browser tests (Playwright, Chromium, Firefox and WebKit) that do not count in that percentage: accessibility, keyboard, CSP, Trusted Types, memory leaks and the documentation site.

Coverage measures which lines run, not that they are well tested; that is why the edge-case tests (extremos, auditoria, seguridad, exportacion) are written from what can go wrong, not from what is left to cover.