Skip to content
nexus-dialogs
GitHub npm

Support, versions and browsers

Which browsers and versions are supported, what happens when a browser feature is missing, how long each version is supported and how to keep an update from breaking your application.

#Browsers

The minimum comes from the native features the library uses. Each feature is tested in Chromium, Firefox and WebKit (Safari's engine) on every change; old versions are not tested separately: the minimums come from each feature's documentation, not from having run them.

FeatureChrome / EdgeFirefoxSafariIf missing
Modal <dialog> (showModal())379815.4Shown as <dialog open> without a top layer or inert background
color-mix()11111316.2Colors derived from the accent are not computed
Constructable stylesheets7310116.4A fallback <style> is used (with a strict CSP it needs configure({ nonce }))
Container queries (@container)10511016Tabs and the timeline don't adapt to their container's width
100dvh10810115.4Without this unit, a very tall dialog is not limited to the visible height of the screen
:has()10512115.4Cosmetic only: the range calendar doesn't highlight the interval and avatar labels lose some padding

Library minimums: Chrome and Edge 111, Firefox 113, Safari 16.4. In Firefox 113 to 120 everything works and only the range highlight in the calendar is lost (:has()).

There is no support for Internet Explorer or for Safari versions earlier than 16.4. Raising one of these minimums counts as a breaking change and is announced in the CHANGELOG.

#Frameworks and environments

What runs in CI (compatibility matrix). The rows come from compat/matriz.json: CI installs each listed version and runs the tests of its wrapper, so what says "runs" is what really runs. npm run compat:check fails if this table, package.json or the README don't match that file.

#Browsers

BrowserMinimumEngine CI runs (e2e)
Chrome and Edge111Chromium
Firefox113Firefox
Safari16.4WebKit

CI runs the e2e tests with the version of each engine that Playwright ships; old versions are not tested separately.

#Frameworks

FrameworkDeclared minimumVersions CI runs
Vue (nexus-dialogs/vue)3.3 or later3.3 (minimum), latest
React (nexus-dialogs/react)18 or later18.0 (minimum), 18 (latest), latest
Angular (nexus-dialogs/angular)16 or later. ESM only.16.0 (minimum), 19, latest

#Node

MinimumVersions CI runsWhat is checked
1818, 20, 22, 24Importing (ESM and CJS) and failing with a clear error without a DOM. The library is built with Node 22.

Types are included and checked with @arethetypeswrong on every change. Importing the library doesn't touch the DOM and opening a dialog on the server fails with an explicit error.

#Versions

#Support

One person maintains the library, so this is good faith, not a contract.

What to expect
VulnerabilitiesAcknowledgement within 7 days and first assessment within 14 (SECURITY.md). The latest 1.x is fixed; 0.x no longer receives fixes
BugsHandled in the latest version. With a minimal case that reproduces it, the fix is much faster
AccessibilityTakes priority over new features
Previous versionsThey don't receive fixes; upgrading from one minor to the next comes with the migration guide in the CHANGELOG
PublishingEach version is uploaded to npm on hold and is not public until its owner approves it with 2FA

What is not promised: a fixed release calendar, support for browsers outside the table or compatibility with third-party patches on the library.

#Use in production

This library was born for internal company systems and has been tested in real use: its SweetAlert2 adapter runs in a production web application for recruiter tracking, where it replaced SweetAlert2 without changing the screens' code. It is one internal, unnamed case: there is still no public external case to back it up, and that is why the limitations say so.

If you use it in a project, even if everything went well, tell us with "I tried it in my project": which dialogs you use, in what kind of application (no sensitive data) and how it went. Each real case is added here, with your permission.

Meanwhile, what backs stability can be checked: unit tests with coverage thresholds, tests in three browsers, axe in every theme, memory leaks, CSP and Trusted Types, and the complete examples running on every change. Size and performance numbers are repeated with npm run bench (Performance).