API reference — Nexis documentation

Core and rendering

Core supplies renderable children, components, layouts, Suspense, Form, SubmitButton, and reactivity re-exports. Renderer converts those nodes to strings or streams with configured render modes.

Browser boundaries

Reactivity exposes state, computed, resource, effect, batch, roots, and cleanup. State adds serializable stores and selectors. Client code resolves scope and installs direct DOM bindings.

Production surface

SEO builds head and discovery artifacts; Actions secures typed mutations; Media transforms responsive assets; createServer, createMiddleware, composeMiddleware, and defineConfig provide the Node production surface; adapters provide Fetch-native delivery; CLI orchestrates the lifecycle.

Security primitives

The first-party security package provides createSession, role and permission guards, and requireAccess for application-owned resource or tenant policy. It intentionally requires the application to own the identity provider, user data, and session persistence.

PRACTICAL LABS

Run this capability.

Each example states the observable output, the boundary that remains your responsibility, and the check that proves the result.

Import from the owning package

TypeScript

import { Link } from '@mohammedaydan/router'
import { createContextScope, state } from '@mohammedaydan/core'
import { createStore } from '@mohammedaydan/state'
import { action } from '@mohammedaydan/actions'

OUTPUT: The dependency graph is explicit and the TypeScript declarations identify the current release contract.
BOUNDARY: Do not import Node-only server code into a browser route or treat internal source as public API.
PROVE IT: Confirm the exact installed declaration before relying on a signature.

VERIFICATION

Prove the contract.

Confirm names and TypeScript signatures against the installed package declarations for the exact release used by your application.