@faqir-ui/core 1.0.0

package/package.json

@@ -0,0 +1,77 @@
+{
+  "name": "@faqir-ui/core",
+  "version": "1.0.0",
+  "description": "Faqir UI runtime engine — the Alpine-style reactive core (faqir-core.js), minified CDN build, and prebuilt per-theme CSS bundles. Zero dependencies.",
+  "type": "module",
+  "main": "./dist/faqir-core.mjs",
+  "types": "./faqir-core.d.ts",
+  "module": "./dist/faqir-core.mjs",
+  "unpkg": "./dist/faqir-core.min.js",
+  "jsdelivr": "./dist/faqir-core.min.js",
+  "//exports": "`.` resolves to dist/faqir-core.mjs — real ESM, `export default` plus one named export per engine member. It must NOT resolve to dist/faqir-core.js: that file is UMD, this package is `\"type\": \"module\"`, and under ESM the UMD wrapper takes its global branch and exports nothing, so the documented `import Faqir from \"@faqir-ui/core\"` failed with `SyntaxError: … does not provide an export named 'default'`. The UMD build is still shipped and is still what `<script src>`, unpkg and jsdelivr load; reach it explicitly at `@faqir-ui/core/faqir-core.js`.",
+  "//require": "Deliberately absent. This package is ESM-only. The `require` condition used to point at the UMD file, which threw ERR_REQUIRE_ESM on Node 18 and 20 — most of the range `engines` promises — because `\"type\": \"module\"` classifies a `.js` file as ESM whatever its contents. Supporting `require` honestly would mean shipping a `.cjs` runtime AND a full-fidelity `.d.cts`, and a half-fidelity one recreates exactly the FalseCJS mismatch this shape was fixed to remove. On Node >=22.12 `require()` falls through to `default` and works; below that it fails with a message that names `import()`, which is the right answer.",
+  "exports": {
+    ".": {
+      "types": "./faqir-core.d.ts",
+      "import": "./dist/faqir-core.mjs",
+      "default": "./dist/faqir-core.mjs"
+    },
+    "./faqir-core.js": {
+      "types": "./faqir-core.d.ts",
+      "default": "./dist/faqir-core.js"
+    },
+    "./faqir-core.mjs": {
+      "types": "./faqir-core.d.ts",
+      "default": "./dist/faqir-core.mjs"
+    },
+    "./faqir-core.min.js": "./dist/faqir-core.min.js",
+    "./sri.json": "./dist/sri.json",
+    "./dist/*": "./dist/*",
+    "./package.json": "./package.json"
+  },
+  "files": [
+    "dist",
+    "faqir-core.d.ts",
+    "src",
+    "examples",
+    "cdn.json",
+    "README.md"
+  ],
+  "sideEffects": [
+    "./dist/faqir-core.mjs",
+    "./dist/faqir-core.js",
+    "./dist/faqir-core.min.js",
+    "./dist/*.css"
+  ],
+  "scripts": {
+    "build": "node ../../scripts/build-core-package.mjs",
+    "prepublishOnly": "node ../../scripts/build-core-package.mjs"
+  },
+  "keywords": [
+    "faqir",
+    "ui",
+    "reactive",
+    "cdn",
+    "runtime",
+    "zero-dependency",
+    "agent-native",
+    "html",
+    "css"
+  ],
+  "license": "MIT",
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/Narcis13/faqir-ui.git",
+    "directory": "packages/core"
+  },
+  "homepage": "https://github.com/Narcis13/faqir-ui/tree/main/packages/core#readme",
+  "bugs": {
+    "url": "https://github.com/Narcis13/faqir-ui/issues"
+  },
+  "engines": {
+    "node": ">=18"
+  },
+  "publishConfig": {
+    "access": "public"
+  }
+}

package/src/cdn-entry.js

@@ -0,0 +1,12 @@
+// CDN classic-script entry for `@faqir-ui/core`.
+//
+// `scripts/build-core-package.mjs` bundles this file with `--format=iife`, so a
+// plain `<script src="faqir-core.min.js">` (no `type="module"`) executes the
+// engine and assigns it to `window.Faqir` — the two-tag CDN story (§10.3).
+//
+// The unminified `dist/faqir-core.js` is the canonical UMD build and remains the
+// entry for `import`/`require`; this wrapper exists only to give the minified
+// classic-script artifact a global.
+import Faqir from "../../../registry/core/faqir-core.js";
+
+(typeof globalThis !== "undefined" ? globalThis : typeof self !== "undefined" ? self : this).Faqir = Faqir;

package/src/esm-entry.js

@@ -0,0 +1,58 @@
+// ESM entry for `@faqir-ui/core` — the target of the `import` condition.
+//
+// WHY THIS FILE EXISTS. `registry/core/faqir-core.js` is a UMD wrapper, and the
+// package is `"type": "module"`. Under ESM neither `exports` nor `module` nor
+// `define` is defined, so the wrapper takes its *global* branch: it assigns
+// `globalThis.Faqir` and exports nothing at all. Pointing the `import`
+// condition at it made the shape both the README and `faqir-core.d.ts`
+// document —
+//
+//     import Faqir from "@faqir-ui/core";
+//
+// — fail at runtime with `SyntaxError: … does not provide an export named
+// 'default'`. Bundling the same factory to real ESM here fixes it at the
+// source: the engine gets `module`/`exports` from the bundler, takes the CJS
+// branch, and its return value becomes an honest module export. No global is
+// touched, so two copies of the package no longer race for `globalThis.Faqir`.
+//
+// The UMD file is still shipped and is still what `<script src>` and the CDN
+// load — see `cdn-entry.js`, which is the same idea for the `iife` format.
+//
+// The named exports below are NOT decorative: they are the whole reason this is
+// a wrapper rather than a re-export, since a UMD default cannot be destructured
+// by a bundler. `tests/build/core-package.test.ts` holds this list against
+// `Object.keys()` of the live engine in both directions, so an engine member
+// added without a line here fails the build.
+import Faqir from "../../../registry/core/faqir-core.js";
+
+export default Faqir;
+
+export const version = Faqir.version;
+
+// ── Reactivity ──
+export const reactive = Faqir.reactive;
+export const effect = Faqir.effect;
+export const batch = Faqir.batch;
+export const untrack = Faqir.untrack;
+export const nextTick = Faqir.nextTick;
+
+// ── Expressions ──
+export const evaluate = Faqir.evaluate;
+export const evaluateAssignment = Faqir.evaluateAssignment;
+
+// ── Registration ──
+export const data = Faqir.data;
+export const store = Faqir.store;
+export const directive = Faqir.directive;
+export const magic = Faqir.magic;
+export const plugin = Faqir.plugin;
+export const controller = Faqir.controller;
+
+// ── Lifecycle ──
+export const start = Faqir.start;
+export const initTree = Faqir.initTree;
+export const destroy = Faqir.destroy;
+
+// ── Inspection ──
+export const inspect = Faqir.inspect;
+export const devtools = Faqir.devtools;