@metreeca/tile
    Preparing search index...
    • Offers a shared status board to nested components.

      The outermost context takes up the issues the page raises on its own account, that is broken scripts and unhandled rejections, and states them among the others: a rejected exchange nobody attended reaches a reader with the status and the explanation its source gave it, rather than as a console entry only developers ever read.

      Nested contexts behave as error boundaries do: each holds the posts and the issues of the components it encloses. The issues of the page belong to no component, so they are stated once, however many contexts are nested.

      Posts stand for as long as the context lives and are cleared by whoever put them up or showed them, so a post is never dropped by a later one; the oldest is dropped on its own where posts stand beyond limit.

      Parameters

      • options: { limit?: number; children: ComponentChildren }

        The number of posts standing at a time, and the components they are offered to

        • Optionallimit?: number

          The number of posts held at a time: putting up a post beyond it drops the oldest; every post is kept if not positive. Taken as the context first renders, so a value given later never reaches it.

          0
          
        • children: ComponentChildren

          The components posts are offered to.

      Returns VNode<{}>

      The nested components, with the posts put up on the interface offered to them

      TypeError If limit is not an integer