aegisnode 0.0.5 → 0.1.1

package/README.md

@@ -2,76 +2,24 @@
 
 ![AegisNode Banner](assets/aegisnode-banner.svg)
 
-AegisNode is a modular, view-first Node.js framework for building web apps, JSON APIs, and hybrid projects without spending the first part of the project wiring the same infrastructure again and again.
-It gives you a structured project layout, runtime injection, CLI scaffolding, and production-ready defaults while still keeping the Node.js and Express ecosystem familiar.
+AegisNode is a modular, view-first Node.js framework for building web apps, JSON APIs, and hybrid projects.
+It gives you a structured project layout, runtime injection, CLI scaffolding, and production-ready defaults so you can start building features instead of first wiring routing, config loading, auth, uploads, and other framework glue.
 
 AegisNode is designed for developers who want more structure than raw Express, but do not want a framework that hides the Node.js runtime behind too many abstractions.
-It keeps the request/response model familiar while organizing the codebase around clear app boundaries, runtime-injected dependencies, and reusable layers such as views, services, models, validators, and subscribers.
+It keeps the request/response model familiar while organizing the codebase around clear app boundaries and reusable layers such as views, services, models, validators, subscribers, and app-local utilities.
 
 It works well for projects that mix server-rendered pages and JSON endpoints, for teams that want a consistent project shape from the start, and for codebases that need built-in support for common backend concerns like auth, uploads, i18n, mail, maintenance mode, and environment-driven configuration.
-The goal is to reduce setup time, remove repetitive infrastructure work, and give the project a cleaner long-term structure without making day-to-day development feel heavy.
-
-## Documentation Guide
-
-If you are new to AegisNode, read this README in this order:
-- Quick Start: create a project, install dependencies, run the server, and understand startup mode rules.
-- Core Concepts And App Structure: understand apps, layers, injected runtime context, and project flow.
-- Common Tasks And Feature Guides: uploads, API apps, auth, templates, i18n, mail, and related features.
-- Full Settings Reference: use this as the complete config manual once you already know what feature you need.
-- Runtime Patterns And Advanced Topics: validators, strict layers, subscribers, and security details.
-
-Standalone HTML handbook:
-- Open `docs/index.html` in a browser for a sidebar-based documentation view.
-
-## How AegisNode Helps
-
-AegisNode helps by standardizing the parts that usually consume time early in a project:
-- project scaffolding and app generation,
-- route and layer organization,
-- dependency injection and shared runtime context,
-- config loading and environment overrides,
-- auth, upload, mail, websocket, and i18n integration,
-- operational helpers such as health checks, maintenance mode, and project diagnostics.
-
-This means you spend less time writing framework glue and more time writing business features.
-
-## Why Use AegisNode
-
-Choose AegisNode if you want a project starter that remains readable as it grows.
-It keeps the development model simple, but adds enough structure and tooling to make larger codebases easier to navigate, extend, and maintain.
-
-Core features:
-
-- CLI generators (`startproject`, `createapp`, `runserver`)
-- App scaffold repair command (`fix`)
-- Startup entry generator (`generateloader`)
-- Project health checker (`doctor`)
-- Dependency updater (`updatedeps`)
-- Maintenance mode with custom HTML responses
-- Generators for app artifacts (`generate view|model|validator|dto|service|subscriber|route`)
-- DI container
-- Event system with subscribers
-- Modular app structure
-- SQL/NoSQL bootstrap via QueryMesh/Mongoose
-- WebSocket bootstrap using Socket.IO
-- Built-in file uploads with size/type limits (`route.upload`)
-- Built-in mail transport wrapper (`mail.send`, `req.aegis.mail.send`)
-- Centralized config and loaders
-- Security headers via Helmet (configurable CSP) + CSRF protection for form submissions
-- Built-in rate limiting for basic DDoS resistance
-- Root route file `routes.js` (not `routes/` folder)
-- Automatic default confirmation page on `/` when no custom `/` route exists
-- App folder uses `views.js` (not `controllers/` folder)
-- `createapp` uses file modules: `views.js`, `models.js`, `validators.js`, `routes.js`, `subscribers.js`, `services.js`, `utils.js`
-- `createapp` also generates app tests in `apps/<app>/tests`
-- EJS templates configurable in `settings.js` with Django-style base layout flow
-- Built-in runtime helpers (`money`, `number`, `dateTime`, `timeElapsed`, `toObjectId`) + `jlive` bridge
-
-`startproject` creates `app.js`, `loader.cjs`, `.env`, `settings.js`, and `routes.js` without creating any default app.
-It does not create `public/` or `logs/`; create your own folders and set them in `settings.js`.
-
-Environment files are loaded automatically before `settings.js` is imported.
-Supported files:
+
+Read this README in this order:
+1. Quick Start: get a project created, installed, and running.
+2. Core Concepts And App Structure: understand where code lives and how layers fit together.
+3. Common Tasks And Feature Guides: jump to the feature you need once the basics are clear.
+4. Full Settings Reference: use this when you already know which config block you are looking for.
+5. Runtime Patterns And Advanced Topics: read this last for middleware, validators, subscribers, and strict-layer behavior.
+
+If you prefer a sidebar-based handbook, open `docs/index.html` in a browser.
+
+Environment files are loaded automatically before `settings.js` or `settings.ts` is imported:
 - `.env`
 - `.env.local`
 - `.env.<NODE_ENV>`
@@ -81,191 +29,132 @@ Shell or hosting-panel environment variables win over values from `.env` files.
 
 ## Quick Start
 
-### CLI
+Use this section to get a project running first. Skip to later sections only when you need a specific feature or configuration block.
+
+### Create A Project
 
 ```bash
 npm install -g aegisnode
 
+mkdir blog && cd blog
 aegisnode startproject blog
-npm --prefix blog install
-aegisnode runserver --project blog
-
-aegisnode createapp users --project blog
-aegisnode fix --app users --project blog
-aegisnode generate view profile --app users --project blog
-aegisnode generate route profile --app users --project blog
-aegisnode generateloader --project blog
-aegisnode doctor --project blog
-aegisnode doctor --app users --project blog
-aegisnode updatedeps --project blog
 ```
 
-`cd blog` is optional. You can run commands from parent folder with `--project blog`.
-
-`createapp`, `fix`, `generate`, `runserver`, `generateloader`, `doctor`, and `updatedeps` are project-level commands.
-Run them from the project root; do not `cd` into `apps/<app>`.
-Startup mode rules:
-- Development (`env === development`): start with `aegisnode runserver` only.
-- Non-development (`env !== development`): start with `node loader.cjs` (or your process manager/host pointing to `loader.cjs`).
-- `node app.js` and `node loader.cjs` are rejected in development mode.
-- `aegisnode runserver` is rejected outside development mode.
-
-### Trust Proxy
-
-If your app runs behind Nginx, Apache, Passenger, or another reverse proxy that terminates HTTPS before the Node process, set top-level `trustProxy` in `settings.js`:
+Create and enter the project directory first. `startproject` scaffolds into the current empty directory; it does not create a nested folder for you.
+Use plain `startproject` for a JavaScript project. Add `--typescript` once if you want the whole scaffold to use `.ts`.
+For a TypeScript project, use `aegisnode startproject blog --typescript` inside the target folder instead.
 
-```js
-export default {
-  trustProxy: 1,
-};
-```
-
-This is the AegisNode equivalent of `app.set('trust proxy', 1)` in raw Express. It makes `req.secure`, `req.protocol`, client IP detection, secure cookies, and HTTPS-aware auth logic behave correctly behind the proxy.
-
-Prefer an exact value such as `1`, `'loopback'`, or a subnet string instead of `true`.
+`startproject` creates `app.js`, `loader.cjs`, `.env`, `settings.js`, and `routes.js` in the current directory without creating any default app.
+Use `startproject --typescript` to generate `app.ts`, `settings.ts`, `routes.ts`, app `*.ts` files, and `tsconfig.json` instead.
+It also creates `public/` and `templates/` so the default `staticDir` and `templates.dir` targets already exist.
+Create any additional folders such as `logs/` yourself when needed.
 
-### Deploy On Phusion Passenger
-
-AegisNode supports Passenger-style startup using the generated `loader.cjs`.
-
-Passenger setup (Apache/Nginx/Plesk/cPanel/etc.):
-1. Set **Application Root** to your project folder.
-2. Set **Startup File** to `loader.cjs`.
-3. Install dependencies in project root (for example: `npm install --omit=dev`).
-4. Set environment variables (at minimum `NODE_ENV=production`; keep `PORT` managed by Passenger).
-5. Restart the Node app from your hosting panel/service.
-
-Plesk note: these map to **Application Root** and **Application Startup File** fields.
-
-HTTPS note:
-- If TLS is terminated by Passenger/Apache/Nginx, keep `https.enabled` off and set top-level `trustProxy` to `1` (or another exact proxy-hop/subnet value) so `req.secure`, secure cookies, and OAuth2 HTTPS checks work correctly.
-- Only enable `https` in `settings.js` when Node itself should serve TLS directly.
-
-How it works:
-- `loader.cjs` imports `app.js`.
-- `app.js` starts AegisNode with project root resolved from its own file location, so it works correctly under Passenger.
-
-
-Generated routes are auto-wired into `apps/<app>/routes.js`.
-`createapp` auto-detects the project root when run inside the project or from a parent folder containing exactly one AegisNode project.
-After `createapp user`, `routes.js` is updated with central mapping style:
-`route.use('/user', user);`
-Only apps declared in `settings.apps` are allowed to load/mount. Startup fails when routes reference an undeclared app.
-`--mount` accepts only safe path segments (`a-z`, `A-Z`, `0-9`, `_`, `-`, `:`).
-
-By default, new app routes are API-ready:
-- `GET /<mount>` list
-- `POST /<mount>` create
-- `GET /<mount>/:id` read
-- `PUT /<mount>/:id` update
-- `DELETE /<mount>/:id` delete
-
-Default flow is `route -> validator -> service -> model`.
-Default app tests generated by `createapp`:
-- `apps/<app>/tests/models.test.js`
-- `apps/<app>/tests/validators.test.js`
-- `apps/<app>/tests/services.test.js`
-- `apps/<app>/tests/routes.test.js`
-
-Run all project tests:
+### Install Dependencies And Run The Server
 
 ```bash
-npm test
+npm install
+aegisnode runserver
 ```
 
-Run project preflight checks:
+If you choose to stay outside the project folder, the project-level commands also accept `--project <path>`.
+
+### Create Your First App
 
 ```bash
-aegisnode doctor
+aegisnode createapp users
+aegisnode generate view profile --app users
+aegisnode generate route profile --app users
 ```
 
-`doctor` checks:
-- Project structure (`settings.js`, `routes.js`, app folders)
-- Startup entry files (`app.js`, `loader.cjs`), with production errors when `loader.cjs` is missing
-- App declarations vs filesystem
-- Security baseline (`appSecret`, csrf/headers/ddos toggles)
-- Auth safety checks (JWT secret, OAuth2 `allowHttp` in production)
-- Template directory availability
+`createapp` updates `settings.apps` and the root `routes.js` or `routes.ts` mapping for you.
+It also generates default app tests under `apps/<app>/tests`.
 
-Run app-level scaffold checks for one app:
+### Startup Mode Rules
 
-```bash
-aegisnode doctor --app users
-```
+- Development (`env === 'development'`): start with `aegisnode runserver`.
+- Non-development (`env !== 'development'`): start with `node loader.cjs`.
+- `node app.js` and `node loader.cjs` are blocked in development mode.
+- `aegisnode runserver` is blocked outside development mode.
 
-App-level doctor focuses on the named app:
-- Missing `views.js`, `models.js`, `services.js`, `validators.js`, `routes.js`, `subscribers.js`, `utils.js`
-- Missing generated test files under `apps/<app>/tests`
-- Missing `settings.apps` declaration for that app
-- Missing central `routes.js` import/mount when `autoMountApps` is off
+### Project Maintenance Commands
 
-Repair a partially missing app scaffold:
+Use these after the project already exists:
 
 ```bash
+aegisnode doctor
+aegisnode doctor --app users
 aegisnode fix --app users
+aegisnode generateloader
+aegisnode updatedeps
 ```
 
-`fix` recreates missing default app files and tests without overwriting existing files. If the app is missing from `settings.apps` or central `routes.js`, it restores those registrations too.
+What they do:
+- `doctor`: checks project structure, startup entry files, app declarations, and security/auth basics.
+- `doctor --app`: checks one app for missing scaffold files, tests, and registrations.
+- `fix --app`: recreates missing app scaffold files without overwriting existing files.
+- `generateloader`: restores `loader.cjs` and `app.js` when startup files are missing.
+- `updatedeps`: rewrites package dependency ranges to the current npm `latest` versions and reinstalls.
 
-Regenerate project startup entry files if needed:
+Run project tests with:
 
 ```bash
-aegisnode generateloader
+npm test
 ```
 
-This restores `loader.cjs` and also recreates `app.js` if it is missing.
+### JavaScript vs TypeScript Projects
 
-Update project dependencies to the current npm `latest` dist-tag:
+The project type is chosen once at `startproject` time:
+- `aegisnode startproject blog` scaffolds a JavaScript project in the current directory
+- `aegisnode startproject blog --typescript` scaffolds a TypeScript project in the current directory
 
-```bash
-aegisnode updatedeps
-```
+After that, the rest of the CLI follows the project automatically:
+- `createapp` generates `views.js` / `services.js` / `routes.js` in JavaScript projects, or `views.ts` / `services.ts` / `routes.ts` in TypeScript projects
+- `generate` creates artifacts with the same extension as the project, for example `profile.view.js` or `profile.view.ts`
+- `fix`, `doctor`, and `generateloader` also check and repair the matching project file type automatically
 
-`updatedeps` rewrites `dependencies`, `devDependencies`, `optionalDependencies`, and
-`peerDependencies` in the project `package.json`, then runs the detected package manager's
-`install`. It skips non-registry specs such as `file:`, `workspace:`, and git/http sources.
+`createapp`, `fix`, `generate`, `runserver`, `generateloader`, `doctor`, and `updatedeps` are project-level commands.
+Run them from the project root; do not `cd` into `apps/<app>`.
 
-### Maintenance Mode
+## Core Concepts And App Structure
 
-Enable maintenance mode in `settings.js` to serve a maintenance route with `503 Service Unavailable`.
-If that route is missing or does not respond, AegisNode renders its internal maintenance fallback view:
+Use this section to understand the project shape before you start adding more features. The goal here is to make it clear where code belongs and what each layer is responsible for.
 
-```js
-export default {
-  maintenance: {
-    enabled: true,
-    route: '/maintenance',
-    excludePaths: ['/health'],
-    retryAfter: 120,
-  },
-};
-```
+### Generated Project Shape
 
-```js
-export default {
-  register(route) {
-    route.get('/maintenance', (req, res) => {
-      res.render('maintenance', {
-        title: 'Scheduled maintenance',
-      });
-    });
-  },
-};
-```
+`startproject` creates the runtime entry files and base config for you in the current directory:
+- JavaScript projects: `app.js`, `loader.cjs`, `.env`, `settings.js`, `routes.js`
+- TypeScript projects: `app.ts`, `loader.cjs`, `.env`, `settings.ts`, `routes.ts`, `tsconfig.json`
 
-Notes:
-- `maintenance.route` is internally rewritten, so requests like `/users` can display your maintenance page without a redirect.
-- If `maintenance.route` is not defined, or the route does not answer, the bundled fallback view is rendered.
-- `excludePaths` lets selected endpoints keep running during maintenance.
-- `retryAfter` sets the HTTP `Retry-After` header.
-- `maintenance: true` uses the built-in default maintenance page.
-- `maintenance: '<html>...</html>'` is still accepted as a shorthand for direct custom HTML.
+`createapp` then adds feature modules under `apps/<app>/`:
+- `views.js` or `views.ts`
+- `models.js` or `models.ts`
+- `services.js` or `services.ts`
+- `validators.js` or `validators.ts`
+- `routes.js` or `routes.ts`
+- `subscribers.js` or `subscribers.ts`
+- `utils.js` or `utils.ts`
+- `tests/`
+
+Other scaffold rules to know:
+- `createapp` auto-detects the project root when you run it inside the project or from a parent folder containing exactly one AegisNode project.
+- New apps are registered in `settings.apps` and mounted in the root `routes.js` or `routes.ts`.
+- Only apps declared in `settings.apps` are allowed to load or mount.
+- `--mount` accepts only safe path segments (`a-z`, `A-Z`, `0-9`, `_`, `-`, `:`).
+- New app routes are generated in an API-ready CRUD shape by default:
+  - `GET /<mount>`
+  - `POST /<mount>`
+  - `GET /<mount>/:id`
+  - `PUT /<mount>/:id`
+  - `DELETE /<mount>/:id`
+- Default app tests generated by `createapp` are:
+  - JavaScript projects: `apps/<app>/tests/models.test.js`, `validators.test.js`, `services.test.js`, `routes.test.js`
+  - TypeScript projects: `apps/<app>/tests/models.test.ts`, `validators.test.ts`, `services.test.ts`, `routes.test.ts`
 
-### Generated Settings Config
+### Generated Settings Shape
 
-`startproject` generates a minimal `settings.js` and runtime defaults fill the rest.
+`startproject` generates a minimal `settings.js` or `settings.ts`, and runtime defaults fill the rest.
 
-Access environment values anywhere with `process.env`:
+Access environment values directly with `process.env` in the settings file:
 
 ```js
 export default {
@@ -276,9 +165,9 @@ export default {
 };
 ```
 
-Injected app layers also receive `env`, so views/services/models/validators/controllers/subscribers/loaders can use `env.MY_NAME` without importing `process.env`.
+Injected app layers also receive `env`, so views, services, models, validators, controllers, subscribers, and loaders can use `env.MY_NAME` without importing `process.env`.
 
-`settings.js` (generated shape):
+Generated shape:
 
 ```js
 export default {
@@ -287,6 +176,13 @@ export default {
   host: process.env.HOST || '0.0.0.0',
   port: process.env.PORT ? Number(process.env.PORT) : 3000,
   trustProxy: false,
+  staticDir: 'public',
+  templates: {
+    enabled: true,
+    engine: 'ejs',
+    dir: 'templates',
+    base: 'base',
+  },
   security: {
     appSecret: process.env.APP_SECRET || '<generated-at-scaffold-time>',
   },
@@ -313,12 +209,11 @@ export default {
 
 Notes:
 - Keep `AEGIS_APPS_START/END` markers; `createapp` updates this list automatically.
-- `startproject` writes a local `.env` with a generated `APP_SECRET` and also embeds the same generated secret in `settings.js` as a fallback.
-- Add optional blocks manually only when needed: `https`, `templates`, `i18n`, `helpers`, `staticDir`, `websocket`, `uploads`, `mail`, `auth`, `api`, `swagger`, `loaders`, `environments`, `architecture`, `security.headers/ddos/csrf`.
+- `startproject` writes a local `.env` with a generated `APP_SECRET` and also embeds the same generated secret in `settings.js` or `settings.ts` as a fallback.
+- The scaffold already includes `staticDir: 'public'` and a default `templates` block, and it creates those directories for you.
+- Add optional blocks only when you need them: `https`, `i18n`, `helpers`, `websocket`, `uploads`, `mail`, `auth`, `api`, `swagger`, `loaders`, `environments`, `architecture`, `security.headers/ddos/csrf`.
 - Any section you omit uses framework defaults from `src/runtime/config.js`.
 
-## Core Concepts And App Structure
-
 ### App File Usage Examples
 
 Each generated app usually contains:
@@ -329,6 +224,8 @@ Each generated app usually contains:
 - `apps/<app>/subscribers.js`
 - `apps/<app>/routes.js`
 
+If the project was created with `--typescript`, the same generated files use `.ts` instead of `.js`.
+
 Usage by file:
 - `views.js`: HTTP handlers (`req`, `res`, `next`). Default signature can be context-first: `handler({ service, validator, services, validators, ... }, req, res, next)`.
   Keep `views.js` thin: prefer only the view class and its imports. Avoid defining extra local helper/utility functions in the view file. Move reusable pure logic to `utils.js` and app workflows to `services.js`.
@@ -540,6 +437,77 @@ export default {
 
 ## Common Tasks And Feature Guides
 
+Use this section once the project is already running and you need a specific feature, integration, or deployment-related behavior.
+
+### Reverse Proxies And Passenger
+
+If HTTPS is terminated by Nginx, Apache, Passenger, or another reverse proxy before the Node process, set top-level `trustProxy` in `settings.js` or `settings.ts`:
+
+```js
+export default {
+  trustProxy: 1,
+};
+```
+
+This is the AegisNode equivalent of `app.set('trust proxy', 1)` in raw Express. It makes `req.secure`, `req.protocol`, client IP detection, secure cookies, and HTTPS-aware auth logic behave correctly behind the proxy.
+
+Prefer an exact value such as `1`, `'loopback'`, or a subnet string instead of `true`.
+
+AegisNode also supports Passenger-style startup using the generated `loader.cjs`.
+
+Passenger setup (Apache, Nginx, Plesk, cPanel, and similar hosts):
+1. Set **Application Root** to your project folder.
+2. Set **Startup File** to `loader.cjs`.
+3. Install dependencies in the project root, for example `npm install --omit=dev`.
+4. Set environment variables. At minimum, make sure the resolved app env is production and let Passenger manage `PORT`.
+5. Restart the Node app from the hosting panel or service manager.
+
+Plesk note: these map to **Application Root** and **Application Startup File** fields.
+
+HTTPS note:
+- If TLS is terminated by Passenger, Apache, or Nginx, keep `https.enabled` off and use `trustProxy`.
+- Only enable `https` in `settings.js` or `settings.ts` when Node itself should serve TLS directly.
+
+How it works:
+- `loader.cjs` imports `app.js` in JavaScript projects or `app.ts` in TypeScript projects.
+- `app.js` or `app.ts` starts AegisNode with project root resolved from its own file location, so the same entry works under process managers and hosting panels.
+
+### Maintenance Mode
+
+Enable maintenance mode in `settings.js` or `settings.ts` to serve a maintenance route with `503 Service Unavailable`.
+If that route is missing or does not respond, AegisNode renders its internal maintenance fallback view.
+
+```js
+export default {
+  maintenance: {
+    enabled: true,
+    route: '/maintenance',
+    excludePaths: ['/health'],
+    retryAfter: 120,
+  },
+};
+```
+
+```js
+export default {
+  register(route) {
+    route.get('/maintenance', (req, res) => {
+      res.render('maintenance', {
+        title: 'Scheduled maintenance',
+      });
+    });
+  },
+};
+```
+
+Notes:
+- `maintenance.route` is internally rewritten, so requests like `/users` can display your maintenance page without a redirect.
+- If `maintenance.route` is not defined, or the route does not answer, the bundled fallback view is rendered.
+- `excludePaths` lets selected endpoints keep running during maintenance.
+- `retryAfter` sets the HTTP `Retry-After` header.
+- `maintenance: true` uses the built-in default maintenance page.
+- `maintenance: '<html>...</html>'` is still accepted as a shorthand for direct custom HTML.
+
 ### File Uploads
 
 AegisNode provides built-in upload middleware on route API as `route.upload`.
@@ -880,7 +848,7 @@ export default {
   },
   security: {
     ddos: {
-      maxRequests: 120,
+      maxRequests: 300,
     },
   },
   environments: {
@@ -1661,6 +1629,8 @@ Then in EJS:
 <!-- SETTINGS_REFERENCE_START -->
 ## Full Settings Reference
 
+Use this section as a config manual. It is intentionally reference-heavy and is easier to use after you already know which feature or runtime block you need to configure.
+
 All fields below are supported in `settings.js`. If you omit a field, AegisNode uses the runtime default.
 
 Merge order used at startup:
@@ -1888,7 +1858,7 @@ security: {
 | --- | --- | --- |
 | `enabled` | `boolean` / `true` | Enable rate limiter. |
 | `windowMs` | `number` / `60000` | Rate limit window in milliseconds. |
-| `maxRequests` | `number` / `120` | Max requests per window per key. |
+| `maxRequests` | `number` / `300` | Max requests per window per key. |
 | `message` | `string` / `'Too many requests, please try again later.'` | JSON error message text. |
 | `statusCode` | `number` / `429` | Response status code when limited. |
 | `standardHeaders` | `boolean` / `true` | Emit modern rate-limit headers. |
@@ -2176,6 +2146,8 @@ Behavior:
 
 ## Runtime Patterns And Advanced Topics
 
+Use this section after the basics are clear. It covers the runtime contracts that matter once you are shaping larger apps or enforcing stricter boundaries.
+
 ### Middleware
 
 Route API supports Express-style middleware chains:
@@ -2541,7 +2513,7 @@ security: {
   ddos: {
     enabled: true,
     windowMs: 60000,
-    maxRequests: 120,
+    maxRequests: 300,
     message: 'Too many requests, please try again later.',
     statusCode: 429,
     standardHeaders: true,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "aegisnode",
-  "version": "0.0.5",
+  "version": "0.1.1",
   "description": "A view-first Node.js framework for modular web apps and JSON APIs with CLI scaffolding, runtime injection, auth, uploads, i18n, mail, and WebSocket support.",
   "type": "module",
   "main": "./src/index.js",
@@ -44,17 +44,18 @@
   },
   "license": "MIT",
   "dependencies": {
-    "ejs": "^3.1.10",
-    "express": "^4.21.2",
-    "express-rate-limit": "^8.3.1",
+    "ejs": "^5.0.2",
+    "express": "^5.2.1",
+    "express-rate-limit": "^8.5.2",
     "helmet": "^8.1.0",
     "jlive": "^0.1.2",
-    "jsonwebtoken": "^9.0.2",
-    "mongoose": "^8.12.1",
-    "multer": "^2.1.0",
-    "nodemailer": "^8.0.2",
-    "querymesh": "^0.0.7",
-    "socket.io": "^4.8.1",
-    "swagger-ui-express": "^5.0.1"
+    "jsonwebtoken": "^9.0.3",
+    "mongoose": "^9.6.2",
+    "multer": "^2.1.1",
+    "nodemailer": "^8.0.7",
+    "querymesh": "^0.1.0",
+    "socket.io": "^4.8.3",
+    "swagger-ui-express": "^5.0.1",
+    "tsx": "^4.22.0"
   }
 }