NebkitProvider

initializes properties like theme and brand as global defaults for its wrapped subtree

applies the system theme right from the first paint of server-rendered HTML

uses the system font stack unless fontFamily names a font the app loads, such as a brand typeface, while sizes and line heights stay on the type scale

can lock global page scroll via the lockGlobalScroll prop, the freed scrollbar width is not compensated, so content that fills the page width can shift by it

sets the reading direction through dir on its root and on portals, so layout, arrow keys, placements and directional icons follow it, left unset it writes nothing and the page direction applies, such as a dir set on <html>

typical usage is to wrap the whole app tree with a single instance and render NebulaKit components anywhere inside it

multiple instances on independently rendered pages are fine, for example separate pages of a multi-page app each mounting their own instance

not meant to be nested

set locale when rendering on the server, so the server and the browser format dates the same