gina 0.1.8-alpha.1 → 0.1.8

package/.github/dependabot.yml

@@ -0,0 +1,12 @@
+version: 2
+updates:
+  - package-ecosystem: "npm"
+    directory: "/"
+    schedule:
+      interval: "weekly"
+    ignore:
+      # Vendored dependencies under framework/v*/ are managed manually.
+      # They are not installed via npm — do not auto-update them.
+      - dependency-name: "*"
+        update-types: ["version-update:semver-patch"]
+    open-pull-requests-limit: 5

package/CHANGELOG.md

@@ -6,6 +6,17 @@ adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html),
 and is generated by [Changie](https://github.com/miniscruff/changie).
 
 
+## 0.1.8 - 2026-03-27
+### Added
+* Added .github/dependabot.yml — weekly npm dependency updates for root package.json; vendored framework deps excluded
+* Added _debugLog / _isDebugLog to server.isaac.js (LOG_LEVEL=debug|trace outputs gray-coded timestamps with [gina:isaac] group tag, matching gna.js and server.js)
+### Changed
+* package.json description updated to: Node.js MVC framework with built-in HTTP/2, multi-bundle architecture, and scope-based data isolation — no Express dependency
+### Fixed
+* Removed swig devDependency declarations (package.json.dist) from git — eliminated 6 Dependabot false-positive alerts (lodash, express, phantomjs are swig test-only deps, never installed or reachable at runtime)
+* Popin overlay stuck active after form submit: data-gina-popin-loading attribute was set on XHR readyState 1/3 but never removed on readyState 4 (response complete), leaving the overlay blocking subsequent interactions. Cleared in xhr.onreadystatechange readyState==4, popinClose, and popinReset.
+* Couchbase connector: @include directives sent raw to Couchbase in dev mode — the dev-mode SQL re-read refreshed the query body without re-expanding @include tokens, causing N1QL syntax errors. Dev-mode re-read now applies the same @include expansion as the startup parser.
+
 ## 0.1.8-alpha.1 - 2026-03-26
 ### Added
 * Config variable interpolation now accepts \${variable} syntax in addition to {variable}. Both forms work in all config files (routing.json, app.json, settings.json, etc.). The {variable} syntax continues to work unchanged — migration to \${variable} is optional and will be documented in a future release.

package/CONTRIBUTING.md

@@ -0,0 +1,190 @@
+# Contributing to Gina
+
+Gina follows a BDFL governance model — see [GOVERNANCE.md](./GOVERNANCE.md) for how decisions are made. Contributions of all experience levels are welcome.
+
+---
+
+## Table of contents
+
+- [Requirements](#requirements)
+- [Getting started locally](#getting-started-locally)
+- [Running the tests](#running-the-tests)
+- [Development environment](#development-environment)
+- [Debugging](#debugging)
+- [Branch model](#branch-model)
+- [Commit style](#commit-style)
+- [Changelog](#changelog)
+- [Pull request checklist](#pull-request-checklist)
+- [Reporting bugs](#reporting-bugs)
+- [Proposing features](#proposing-features)
+
+---
+
+## Requirements
+
+| Requirement | Version |
+| --- | --- |
+| OS | macOS or Linux (Windows: Docker only) |
+| Node.js | >= 18 |
+| npm | >= 8 |
+| Changie | >= 1.24 |
+
+---
+
+## Getting started locally
+
+Gina must be installed globally — the CLI and framework bootstrapper expect to run from the npm global prefix. Contributors clone directly into that location instead of using `npm install -g .`.
+
+#### 1. Find your global prefix
+
+```bash
+npm config get prefix --quiet
+```
+
+The default is `/usr/local` (system) or `~/.npm-global` (user). The target directory is `${prefix}/lib/node_modules/gina`.
+
+#### 2. Clone into the prefix
+
+```bash
+cd $(npm config get prefix)/lib/node_modules
+git clone https://github.com/Rhinostone/gina.git gina
+cd gina && git checkout develop
+```
+
+#### 3. Run the install scripts
+
+```bash
+node ./script/pre_install.js
+node ./script/post_install.js
+```
+
+#### 4. Verify
+
+```bash
+gina version
+```
+
+---
+
+## Running the tests
+
+The test suite uses Node's built-in `node:test` runner — no additional test dependencies needed.
+
+```bash
+# Run all tests
+node --test test/**/*.test.js
+
+# Run a single file
+node --test test/core/controller.test.js
+```
+
+---
+
+## Development environment
+
+When contributing to the framework, use the `dev` environment. It enables hot-reload, the debug toolbar, and verbose logging that makes it easier to follow what the framework is doing internally.
+
+```bash
+gina framework:set --env=dev
+```
+
+This sets the default environment so you can omit `--env=dev` from subsequent commands. To start the framework:
+
+```bash
+gina start
+```
+
+To follow logs in real time:
+
+```bash
+gina tail --follow
+```
+
+To revert to production defaults:
+
+```bash
+gina framework:set --env=prod
+```
+
+---
+
+## Debugging
+
+### Framework
+
+```bash
+gina start --inspect-gina
+```
+
+### Bundle
+
+```bash
+gina bundle:restart <bundle_name> @<project_name> --inspect=<port_number>
+```
+
+---
+
+## Branch model
+
+| Branch | Purpose |
+| --- | --- |
+| `master` | Stable — merged from `develop` via PR at release time |
+| `develop` | Working branch — all PRs target this branch |
+
+Always branch from `develop` and open your PR against `develop`.
+
+---
+
+## Commit style
+
+Use imperative or gerund sentences, matching the existing log:
+
+```text
+Fixed GlobalContext::whisper() memory leak
+Added _debugLog to server.isaac.js
+Allowing bundle:build to build for dev env
+```
+
+- One logical change per commit
+- No references to AI tools in commit messages, comments, or files
+
+---
+
+## Changelog
+
+Gina uses [changie](https://changie.dev) for changelog management. After any user-facing change, run:
+
+```bash
+changie new
+```
+
+Pick the kind (`Added`, `Changed`, `Fixed`, `Removed`, `Security`) and write the body from the user's perspective. Do **not** edit `CHANGELOG.md` directly — changie generates it at release time from entries in `.changes/unreleased/`.
+
+---
+
+## Pull request checklist
+
+Before opening a PR against `develop`:
+
+- [ ] Tests pass — `node --test test/**/*.test.js`
+- [ ] New behaviour is covered by a test (or an explanation is provided for why it cannot be)
+- [ ] A `changie new` entry exists for any user-facing change
+- [ ] Commit messages follow the style above
+- [ ] Docs updated if public API, CLI, or config schema changed
+
+---
+
+## Reporting bugs
+
+Open a [GitHub issue](https://github.com/Rhinostone/gina/issues) and include:
+
+- Node.js version (`node --version`)
+- Gina version (`gina --version`)
+- Minimal reproduction steps
+- Expected vs actual behaviour
+
+---
+
+## Proposing features
+
+Open a GitHub issue describing the use case **before** writing code. Features that align with the [roadmap](./ROADMAP.md) and architecture are most likely to be accepted. Significant API changes go through a public discussion period before being finalised.

package/GOVERNANCE.md

@@ -0,0 +1,20 @@
+# Governance
+
+Gina follows the **BDFL** (Benevolent Dictator For Life) model with a commitment to transparency.
+
+Gina is developed and maintained by **Martin Luther** ([Rhinostone](https://www.rhinostone.com/)). Final decisions on direction, API design, and releases rest with the maintainer. Community contributions and RFCs are welcome and taken seriously.
+
+## How decisions are made
+
+- **Patches and bug fixes** — reviewed and merged by the maintainer. Open a pull request against `develop`.
+- **New features** — open a GitHub issue describing the use case before writing code. Features that align with the roadmap and architecture are most likely to be accepted.
+- **Breaking changes and API design** — decided by the maintainer after considering community input. Significant changes go through a public discussion period on GitHub before being finalised.
+- **Releases** — scheduled and cut by the maintainer following the [roadmap](./ROADMAP.md).
+
+## Contributing
+
+See [CONTRIBUTING.md](./CONTRIBUTING.md) for how to set up the project locally, the commit style, and the PR checklist.
+
+## Code of Conduct
+
+Be respectful. Contributions of all experience levels are welcome.

package/README.md

@@ -229,7 +229,7 @@ Gina is shipped with [Swig](https://node-swig.github.io/swig-templates/) as the
 
 Please, note that you have 2 types of environments : one for the framework, and one for your project & your bundles.
 
-> By default, Gina (the framework) comes with 2 environments : `dev` and `prod`. The default is `prod`. If you are [contributing](./README-4Contributors.md) to the framework or prototyping your application or service, we advise using the `dev` environment.
+> By default, Gina (the framework) comes with 2 environments : `dev` and `prod`. The default is `prod`. If you are [contributing](./CONTRIBUTING.md) to the framework or prototyping your application or service, we advise using the `dev` environment.
 >
 > ```tty
 > gina framework:set --env=dev
@@ -619,6 +619,10 @@ More documentation and tutorials are coming soon !
 
 For the full documentation, visit [https://gina.io/docs/](https://gina.io/docs/)
 
+## Governance
+
+Gina is led by Martin Luther (Rhinostone). Final decisions on direction, API design, and releases rest with the maintainer. Community contributions and RFCs are welcome and taken seriously. See [GOVERNANCE.md](./GOVERNANCE.md) for details.
+
 ## License (MIT)
 
 Copyright © 2009-2026 [Rhinostone](http://www.rhinostone.com/)

package/ROADMAP.md

@@ -11,10 +11,11 @@ This roadmap covers planned features, architectural improvements, new connectors
 | Period | Version | Focus |
 | --- | --- | --- |
 | **Apr 2026** | `0.1.8` ✅ | Scaffold correctness · K8s support · Dependency injection · Automatic version migration |
-| **Q2 2026** | `0.2.0` | Stability · WatcherService · Redis & SQLite connectors · K8s session storage |
-| **Q3 2026** | `0.3.0` | Async/await · Dev hot-reload · MySQL & PostgreSQL connectors · AI Phase 2 |
-| **Q4 2026** | `0.4.0` | TypeScript declarations · AI agents (OpenAPI, MCP) · ScyllaDB connector |
+| **Q2 2026** | `0.2.0` | Stability · WatcherService · Redis & SQLite connectors · K8s session storage · Startup cache |
+| **Q3 2026** | `0.3.0` | Async/await · Dev hot-reload · MySQL & PostgreSQL connectors · AI Phase 2 · Tutorials · Mobile backend guide · Route radix tree |
+| **Q4 2026** | `0.4.0` | TypeScript declarations · AI agents (OpenAPI, MCP) · ScyllaDB connector · PWA scaffold · Advanced tutorial · Website redesign · Bun investigation |
 | **Q1 2027** | `0.5.0` | ESM support · Template engine migration · Structured logging |
+| **Q3 2027** | `1.0.0` | First stable release — Windows alpha compatibility is a hard gate |
 
 ---
 
@@ -24,6 +25,7 @@ This roadmap covers planned features, architectural improvements, new connectors
 | --- | --- | --- | --- |
 | ✅ | **Automatic version migration** — Upgrading or downgrading gina (e.g. `0.1.x → 0.2.0`, `0.5.x → 1.0.0`) automatically migrates `~/.gina/` config to the new version on first startup. Downgrade is free — old version data is never removed. | `0.1.8` | 2026-03-26 |
 | 📋 | **`watchers.json`** — First-class bundle config for file watchers. Declare watchers on config files with event-based notification (no polling). Foundation for the dev-mode hot-reload system. | `0.2.0` | Q2 2026 |
+| 📋 | **PWA scaffold** — `gina bundle:add` drops `manifest.json`, a service worker stub (`sw.js`), and the required `<meta>` / `<link>` tags into the bundle boilerplate. Zero runtime dependency. Enables Gina apps to be installed on mobile as PWAs without additional tooling. | `0.4.0` | Q4 2026 |
 
 ---
 
@@ -63,7 +65,7 @@ This roadmap covers planned features, architectural improvements, new connectors
 | Status | Feature | Version | Target |
 | --- | --- | --- | --- |
 | 📋 | **ESM compatibility layer** — Dual CJS/ESM entry points via `"exports"` in `package.json`. Framework internals stay CJS; public API gets ESM re-exports. | `0.5.0` | Q1 2027 |
-| 📋 | **Template engine migration** — Replace the abandoned Swig 1.4.2 with a maintained engine. Leading candidate: Nunjucks (identical Jinja2-style syntax — existing templates require no changes). | `0.5.0` | Q1 2027 |
+| 📋 | **Pluggable template engine** — Swig 1.4.2 stays fully integrated and remains the default. Nunjucks added as a supported alternative (opt-in per project via config). The render layer is abstracted behind a common interface so both engines co-exist. Switching to Nunjucks requires a per-project migration guide (breaking differences: `{% parent %}` → `{{ super() }}`, filter renames, autoescape default, `date` format strings, no `{% spaceless %}` — see docs). | `0.5.0` | Q1 2027 |
 | 📋 | **Structured logging** — JSON log output (`{ level, message, bundle, requestId, durationMs }`). Additive — existing consumers are unaffected. Enables log aggregation (Loki, Datadog, CloudWatch). | `0.5.0` | Q1 2027 |
 
 ---
@@ -121,4 +123,43 @@ New database connectors follow the same interface as the existing Couchbase conn
 
 ---
 
-*Last updated: 2026-03-26 · To suggest a feature, [open an issue](https://github.com/Rhinostone/gina/issues).*
+## Performance
+
+| Status | Feature | Version | Target | Notes |
+| --- | --- | --- | --- | --- |
+| 📋 | **`NODE_COMPILE_CACHE` — V8 bytecode startup cache** | `0.2.0` | Q2 2026 | Node.js 22.8+ caches compiled V8 bytecode to disk. Set once at startup — 30–60% faster cold start on subsequent runs with zero code changes to user bundles. No-op on Node < 22.8, so safe to ship unconditionally. |
+| 📋 | **Route radix tree — compile `routing.json` at startup** | `0.3.0` | Q3 2026 | Current router does linear matching against `routing.json` on every request. Pre-compile routes into a radix tree at bundle startup for O(log n) matching. 2–3x faster routing layer. Internal change — no user-facing API change. |
+| 📋 | **Bun runtime compatibility investigation** | `0.4.0` | Q4 2026 | Prototype Gina under Bun. Two blockers to verify: `require.cache` deletion (dev hot-reload) and `node:http2` completeness. If both pass, Bun gives 3–10x faster startup and meaningful throughput gains. Deliverable: a compatibility report. |
+
+---
+
+## Windows
+
+Windows compatibility is a hard requirement for `1.0.0`. The alpha scope covers all core features: install, scaffold, bundle start/stop, routing, rendering, and basic CLI. Full production-grade parity is post-1.0.0.
+
+| Status | Feature | Version | Target |
+| --- | --- | --- | --- |
+| 📋 | **Windows alpha compatibility** — Install scripts, path handling, symlinks, and bundle lifecycle (start/stop/restart) work correctly on Windows. `bin/gina.bat` kept in sync with `bin/gina`. CI Windows runner required before this can be marked done. Out of scope for alpha: full build system (bash-based), Windows service integration, production-grade process management. | `1.0.0` | Q3 2027 |
+
+---
+
+## Tutorials
+
+| Status | Tutorial | Duration | Version | Target |
+| --- | --- | --- | --- | --- |
+| 📋 | **Using Gina as a mobile backend** — REST API patterns, JSON-only bundles, token auth, CORS, HTTP/2, and the path to OpenAPI/MCP for SDK generation. Docs only — no code changes. | — | `0.3.0` | Q3 2026 |
+| 📋 | **Beginner** — Your first Gina app: install, scaffold, one route, one controller, browser response. Starts from `gina new` — no prior project needed. | 5 min | `0.3.0` | Q3 2026 |
+| 📋 | **Intermediate** — Multi-bundle setup, routing with URL params, entity + connector wiring, template rendering, form handling. Starts from scratch. | ~30 min | `0.3.0` | Q3 2026 |
+| 📋 | **Advanced** — Full production project: authentication, scoped data isolation, async/await, HTTP/2, structured logging, Docker/K8s deployment. Starts from the intermediate tutorial's finished state. | ~60 min | `0.4.0` | Q4 2026 |
+
+---
+
+## Website
+
+| Status | Feature | Version | Target |
+| --- | --- | --- | --- |
+| 📋 | **Official website redesign + docs integration** — Refactor gina.io as a proper project homepage (landing page, feature highlights, showcase) with the documentation fully integrated. Single coherent web presence. Prerequisite: tutorials complete. | `0.4.0` | Q4 2026 |
+
+---
+
+*Last updated: 2026-03-27 · To suggest a feature, [open an issue](https://github.com/Rhinostone/gina/issues).*

package/framework/v0.1.8/VERSION

@@ -0,0 +1 @@
+0.1.8

package/framework/{v0.1.8-alpha.1 → v0.1.8}/core/asset/plugin/dist/vendor/gina/js/gina.js

@@ -21590,6 +21590,16 @@ define('gina/popin', [ 'require', 'vendor/uuid', 'jquery', 'lib/domain', 'lib/me
                         }
                     }
                     if (xhr.readyState == 4) {
+                        // Fixed: clear loading state on response complete — data-gina-popin-loading
+                        // was set on readyState 1|3 but never removed, leaving the overlay blocked.
+                        $popin.target.removeAttribute('data-gina-popin-loading');
+                        if ($popinTrigger) {
+                            if ( /^A$/i.test($popinTrigger.tagName) ) {
+                                $popinTrigger.removeAttribute('aria-disabled');
+                            } else {
+                                $popinTrigger.removeAttribute('disabled');
+                            }
+                        }
                         // 200, 201, 201' etc ...
                         var result = null;
 
@@ -22079,6 +22089,9 @@ define('gina/popin', [ 'require', 'vendor/uuid', 'jquery', 'lib/domain', 'lib/me
                         $el.className                           = $el.className.replace(/\sgina-popin-is-active|gina-popin-is-active|gina-popin-is-active\s/, '');
                         $el.innerHTML                           = '';
                     }
+                    // Fixed: clear loading state on reset — defensive cleanup for navigation
+                    // within a popin that was in loading state when reset was called.
+                    $el.removeAttribute('data-gina-popin-loading');
 
                     // removing from FormValidator instance
                     if ($validatorInstance) {
@@ -22188,6 +22201,9 @@ define('gina/popin', [ 'require', 'vendor/uuid', 'jquery', 'lib/domain', 'lib/me
                             $popinTrigger.removeAttribute('disabled', true);
                         }
                     }
+                    // Fixed: clear loading state on explicit close — defensive cleanup in case
+                    // the popin is closed before the XHR completes or after a non-XHR flow.
+                    $el.removeAttribute('data-gina-popin-loading');
                     triggerEvent(gina, $popin.target, 'close.'+ $popin.id, $popin);
                 }
             }