nodejs-store 2.0.1 → 2.0.3

package/README.md

@@ -13,6 +13,8 @@
 > Also looking for the Python version? See [`py-store`](https://github.com/coenddt/py-store) (pip `storepy`). Both are thin hosts over the shared Rust engine [`rust-store`](https://github.com/coenddt/rust-store).
 > 中文文档见 [README.zh-CN.md](README.zh-CN.md)。
 
+**Documentation site:** <https://coenddt.github.io/nodejs-store/> — every scenario walkthrough with runnable code and the engine's exact limits, one indexable page per scenario.
+
 ---
 
 ## Table of contents

package/llms-full.txt

@@ -482,3 +482,25 @@ and computed columns built in.
 | Migration / DDL engine | no (introspection read-only) | no | yes | yes | yes |
 | Static type generation | no (runtime JSON, cross-language parity) | no | yes | partial | yes |
 | Shared native core across Node and Python | yes (Rust `rust-store`) | no | no | no | no |
+
+---
+
+## 15. Scenario walkthroughs
+
+Step-by-step use cases live in
+[`doc/use-cases/`](https://github.com/coenddt/nodejs-store/tree/main/doc/use-cases):
+
+1. **Multi-tenant SaaS** — bind a schema to `(source, namespace, collection)` and re-target each
+   request with a trusted `{ source, namespace }` route override.
+2. **AI data-QA agent** — compile and validate a GQL plan with `buildPipeline()` before
+   executing it, and capture degraded / non-pushdownable paths with `setFeedbackSink()`.
+3. **MongoDB → PostgreSQL migration** — same schema, same GQL, only the `init()` datasource
+   changes; introspect the physical structure read-only with `syncSchema()`.
+4. **Admin CRUD backend** — schema-driven CRUD with computed columns, soft-delete archives,
+   role whitelists, the `creator` pseudo-role and `queryWithCount` pagination.
+5. **Avoiding N+1 reads** — one nested GQL read instead of a parent-then-children loop (a single
+   `$lookup` aggregation on MongoDB, a single `LEFT JOIN` statement on SQL), including when the
+   planner switches to a two-phase read.
+6. **Serverless and connection reuse** — hoist `init()` and schema registration, keep the driver
+   client warm across invocations, and isolate each request with `setContext` plus fail-secure
+   `setRequireContext(true)`.

package/llms.txt

@@ -21,9 +21,10 @@
 
 ## Docs
 
+- [Documentation site](https://coenddt.github.io/nodejs-store/): the scenario walkthroughs as individual, indexable pages — the fastest way in
 - [README](https://github.com/coenddt/nodejs-store#readme): full overview, quick start, GQL syntax, API, schema reference, FAQ
 - [Chinese README](https://github.com/coenddt/nodejs-store/blob/main/README.zh-CN.md): 中文文档
-- [Use cases](https://github.com/coenddt/nodejs-store/tree/main/doc/use-cases): scenario walkthroughs (multi-tenant SaaS, AI data-QA, cross-database migration, admin CRUD)
+- [Use cases](https://github.com/coenddt/nodejs-store/tree/main/doc/use-cases): scenario walkthroughs (multi-tenant SaaS, AI data-QA, cross-database migration, admin CRUD, avoiding N+1 reads, serverless connection reuse)
 - [Scenario test suite](https://github.com/coenddt/nodejs-store/tree/main/example/course-platform): real-data, four-backend scenario cases (fields, relations, computes, permissions, aggregation, boundaries)
 - [CHANGELOG](https://github.com/coenddt/nodejs-store/blob/main/CHANGELOG.md)
 

package/package.json

@@ -1,8 +1,9 @@
 {
   "name": "nodejs-store",
-  "version": "2.0.1",
+  "version": "2.0.3",
   "description": "Multi-backend data layer for Node.js (MongoDB, MySQL, SQLite, PostgreSQL): pure JSON schemas, GQL tree queries compiled to a single native query, GROUP BY/HAVING aggregation, computed columns, soft-delete and role-based access control",
   "main": "src/index.js",
+  "homepage": "https://coenddt.github.io/nodejs-store/",
   "files": [
     "src",
     "README.md",
@@ -41,6 +42,10 @@
     "group-by",
     "computed-columns",
     "soft-delete",
+    "ai-agent",
+    "llm-tool",
+    "query-validation",
+    "natural-language-query",
     "node"
   ],
   "author": "leo <coen_ddt@qq.com>",