@jexs/server

Node.js server runtime for Jexs — HTTP, routing, database (SQLite / MySQL via knex), sessions, OAuth, email, web-push, WebSocket, Tailwind, file I/O, caching.

Your whole server — entry point, request handlers, queries, sessions, email templates — is JSON, loaded and resolved per request.

Part of Jexs.

Install

npm install @jexs/server @jexs/core

What's inside

Server — a small wrapper around Node's http and ws servers. Started declaratively from JSON via ListenNode.

Nodes (serverNodes):

| Node | Keys | Purpose | |---|---|---| | ListenNode | listen | Start the HTTP server; can auto-serve the @jexs/client bundle | | RouterNode | routes | Path-based routing with :param capture | | FileNode | file, directory | Load JSON files as sub-templates, list/read/write files | | DatabaseNode | database | Configure named connections (SQLite, MySQL) | | QueryNode | query-select, query-insert, query-upsert, query-update, query-delete, query-count, query-create, query-drop, query-alter | DB queries | | SchemaNode | schema | Define/validate row schemas | | SessionNode | session | Cookie-backed sessions | | CryptoNode | hash, verify, random-bytes, jwt-sign, jwt-verify, ... | Crypto helpers | | OAuthNode | oauth | Generic OAuth2 (Google, GitHub, ...) | | EmailNode | email-send | SMTP via nodemailer | | WebPushNode | push-send, push-vapid | Browser push | | WebSocketNode | ws-broadcast, ws-send, ws-handle | WebSocket server | | CacheNode | cache-get, cache-set, cache-del | Memory / Redis / Memcached | | TailwindNode | tailwind | On-demand Tailwind CSS generation | | TranslationNode | translate | i18n | | DeferNode | defer | Run steps after the response is sent | | StdioNode | stdin, stdout, stderr, exit | Process I/O |

Quick example — full server in JSON

src/app.json:

[
  { "database": { "default": { "client": "sqlite", "filename": "data.db" } } },

  { "listen": 3000, "client": true, "do": [
    { "session": "load" },

    { "routes": {
      "methods": { "GET": { "file": "pages/home.json" } },
      "children": {
        "api": { "children": {
          "users": { "methods": {
            "GET": { "query-select": "users", "orderBy": { "id": "desc" }, "limit": 50 },
            "POST": {
              "body": { "type": "object", "required": ["name"], "properties": { "name": { "type": "string" } } },
              "query-insert": "users", "data": { "var": "$request.body" }
            }
          } }
        } },

        "users": { "children": {
          "*": {
            "paramName": "id",
            "paramRegex": "\\d+",
            "methods": { "GET": { "file": "pages/user.json" } }
          }
        } }
      }
    } }
  ] }
]

Routes are a tree, not flat path strings: methods handles the current path (keyed by HTTP verb), children nests path segments, * captures a single segment under paramName (constrained by an optional paramRegex), and ** captures the remainder. A captured param is exposed to the handler as a top-level context var ($id above), the query string as $request.query, and the parsed body as $request.body. A handler may declare query and/or body JSON Schemas — validated against $request.query / $request.body, returning a 400 on failure.

Run with tsx src/index.ts (or whatever entry boots Server):

import { createResolver, coreNodes } from "@jexs/core";
import { Server, serverNodes } from "@jexs/server";

const resolve = createResolver([...coreNodes, ...serverNodes]);
const server = new Server(resolve);
server.setEntryFile("/app.json");
await server.start();

Or scaffold the whole thing with npm create @jexs my-app.

License

MIT