Web

Planned, not built. A niso page is a web page, so the plan for the web is to use the browser’s own DOM with no renderer at all: niso’s custom elements would ship as web components, and platform-prefixed CSS properties would be ignored, as browsers ignore unknown properties (DECISIONS.md, Targets).

Nothing for this target is on main yet: no web component package and no build for it. Today you can still open most niso pages in a browser while developing, since they’re HTML and CSS. What won’t work there is what the host adds: native controls, surfaces, native modules and the platform’s design tokens.