@_linked/primitives 1.3.0 → 1.3.2

package/CHANGELOG.md

@@ -1,5 +1,37 @@
 # @\_linked/primitives
 
+## 1.3.2
+
+### Patch Changes
+
+- [#37](https://github.com/linked-fw/primitives/pull/37) [`d7803e0`](https://github.com/linked-fw/primitives/commit/d7803e09f303015f6ba4f14ef3d610e7cda0c289) Thanks [@flyon](https://github.com/flyon)! - Give this package its own linked identity
+
+  `src/package.ts` re-exported core's decorators verbatim and declared
+  `packageName` as a bare literal that nothing was bound to, so everything
+  declared here registered under `@_linked/core`: the `radix` ontology landed in
+  core's entry in the package tree, and the next `@linkedShape` added here would
+  silently have been given a `.../shape/core/...` IRI. `Server.call` routes on
+  the package name a shape carries, so one naming the wrong package is simply
+  unreachable.
+
+  **No shape IRI changes**, because no shape is decorated here today — that is
+  why this is a patch and not a minor. The only visible change is where the
+  `radix` ontology is registered in the package tree.
+
+  Same defect and same fix as linked-fw/owl#26, where shapes did exist and the
+  IRIs did change.
+
+## 1.3.1
+
+### Patch Changes
+
+- [#34](https://github.com/linked-fw/primitives/pull/34) [`6514c31`](https://github.com/linked-fw/primitives/commit/6514c31aef96a8b4d087e1edf48aa86abe693b87) Thanks [@flyon](https://github.com/flyon)! - Add a root `types` field so a bare import gets types under node10 resolution.
+
+  There was no `types`/`typings` field at all, so a `moduleResolution: node10` consumer doing
+  `import … from '@_linked/primitives'` got `TS2307` — `exports` is ignored under node10. The value
+  `index.d.ts` is redirected by the existing `typesVersions` to `lib/esm/index.d.ts`, matching the
+  sibling packages.
+
 ## 1.3.0
 
 ### Minor Changes

package/lib/cjs/package.d.ts

@@ -1,3 +1,19 @@
-import { getPackageShape, linkedOntology, linkedShape, linkedUtil, packageExports, registerPackageExport, registerPackageModule } from '@_linked/core/package';
-export declare const packageName: string;
-export { getPackageShape, linkedOntology, linkedShape, linkedUtil, packageExports, registerPackageExport, registerPackageModule, };
+/**
+ * This package's own linked identity.
+ *
+ * It used to re-export core's decorators verbatim and declare `packageName`
+ * as a bare literal that nothing was bound to. The decorators therefore came
+ * from `corePackage`, so everything declared here registered under
+ * `@_linked/core`: this package's ontology landed in core's entry in the
+ * package tree, and the next shape added here would silently have been given a
+ * `.../shape/core/...` IRI. That IRI is persisted data and `Server.call`
+ * routes on the package name inside it, so a shape naming the wrong package is
+ * simply unreachable.
+ *
+ * No shape is decorated here today, so nothing was mis-registered — the cost
+ * was waiting for the first one. Same defect, same fix, as linked-fw/owl#26.
+ */
+export declare const linkedShape: {
+    <T extends typeof import("@_linked/core/shapes/Shape").Shape>(constructor: T): void;
+    <T extends typeof import("@_linked/core/shapes/Shape").Shape>(config?: import("@_linked/core/utils/Package").ShapeConfig): (constructor: T) => void;
+}, linkedUtil: (constructor: any) => any, linkedOntology: (allFileExports: any, nameSpace: (term: string) => import("@_linked/core/utils/NodeReference").NodeReferenceValue, suggestedPrefixAndFileName: string, loadDataFunction?: () => Promise<any>, dataSource?: string | string[]) => void, registerPackageExport: (exportedObject: any) => void, registerPackageModule: (_module: any) => void, getPackageShape: (name: string) => import("@_linked/core/shapes/Shape").ShapeConstructor | undefined, packageExports: any, packageName: string;

package/lib/cjs/package.js

@@ -1,13 +1,22 @@
 "use strict";
+var _a;
 Object.defineProperty(exports, "__esModule", { value: true });
-exports.registerPackageModule = exports.registerPackageExport = exports.packageExports = exports.linkedUtil = exports.linkedShape = exports.linkedOntology = exports.getPackageShape = exports.packageName = void 0;
-const package_1 = require("@_linked/core/package");
-Object.defineProperty(exports, "getPackageShape", { enumerable: true, get: function () { return package_1.getPackageShape; } });
-Object.defineProperty(exports, "linkedOntology", { enumerable: true, get: function () { return package_1.linkedOntology; } });
-Object.defineProperty(exports, "linkedShape", { enumerable: true, get: function () { return package_1.linkedShape; } });
-Object.defineProperty(exports, "linkedUtil", { enumerable: true, get: function () { return package_1.linkedUtil; } });
-Object.defineProperty(exports, "packageExports", { enumerable: true, get: function () { return package_1.packageExports; } });
-Object.defineProperty(exports, "registerPackageExport", { enumerable: true, get: function () { return package_1.registerPackageExport; } });
-Object.defineProperty(exports, "registerPackageModule", { enumerable: true, get: function () { return package_1.registerPackageModule; } });
-exports.packageName = { packageName: '@_linked/primitives' }.packageName;
+exports.packageName = exports.packageExports = exports.getPackageShape = exports.registerPackageModule = exports.registerPackageExport = exports.linkedOntology = exports.linkedUtil = exports.linkedShape = void 0;
+const Package_1 = require("@_linked/core/utils/Package");
+/**
+ * This package's own linked identity.
+ *
+ * It used to re-export core's decorators verbatim and declare `packageName`
+ * as a bare literal that nothing was bound to. The decorators therefore came
+ * from `corePackage`, so everything declared here registered under
+ * `@_linked/core`: this package's ontology landed in core's entry in the
+ * package tree, and the next shape added here would silently have been given a
+ * `.../shape/core/...` IRI. That IRI is persisted data and `Server.call`
+ * routes on the package name inside it, so a shape naming the wrong package is
+ * simply unreachable.
+ *
+ * No shape is decorated here today, so nothing was mis-registered — the cost
+ * was waiting for the first one. Same defect, same fix, as linked-fw/owl#26.
+ */
+_a = (0, Package_1.linkedPackage)('@_linked/primitives'), exports.linkedShape = _a.linkedShape, exports.linkedUtil = _a.linkedUtil, exports.linkedOntology = _a.linkedOntology, exports.registerPackageExport = _a.registerPackageExport, exports.registerPackageModule = _a.registerPackageModule, exports.getPackageShape = _a.getPackageShape, exports.packageExports = _a.packageExports, exports.packageName = _a.packageName;
 //# sourceMappingURL=package.js.map

package/lib/cjs/package.js.map

@@ -1 +1 @@
-{"version":3,"file":"package.js","sourceRoot":"","sources":["../../src/package.ts"],"names":[],"mappings":";;;AAAA,mDAQ+B;AAK7B,gGAZA,yBAAe,OAYA;AACf,+FAZA,wBAAc,OAYA;AACd,4FAZA,qBAAW,OAYA;AACX,2FAZA,oBAAU,OAYA;AACV,+FAZA,wBAAc,OAYA;AACd,sGAZA,+BAAqB,OAYA;AACrB,sGAZA,+BAAqB,OAYA;AATR,mBAAW,GAAK,EAAE,WAAW,EAAE,qBAAqB,EAAE,aAAC"}
+{"version":3,"file":"package.js","sourceRoot":"","sources":["../../src/package.ts"],"names":[],"mappings":";;;;AAAA,yDAA0D;AAE1D;;;;;;;;;;;;;;GAcG;AACU,KAST,IAAA,uBAAa,EAAC,qBAAqB,CAAC,EARtC,mBAAW,mBACX,kBAAU,kBACV,sBAAc,sBACd,6BAAqB,6BACrB,6BAAqB,6BACrB,uBAAe,uBACf,sBAAc,sBACd,mBAAW,kBAC4B"}

package/lib/cjs/package.json

@@ -10,7 +10,7 @@
     "type": "git",
     "url": "git+https://github.com/linked-fw/primitives.git"
   },
-  "version": "1.3.0",
+  "version": "1.3.2",
   "packageManager": "npm@11.19.1",
   "linkedPackage": true,
   "license": "ISC",

package/lib/esm/package.d.ts

@@ -1,3 +1,19 @@
-import { getPackageShape, linkedOntology, linkedShape, linkedUtil, packageExports, registerPackageExport, registerPackageModule } from '@_linked/core/package';
-export declare const packageName: string;
-export { getPackageShape, linkedOntology, linkedShape, linkedUtil, packageExports, registerPackageExport, registerPackageModule, };
+/**
+ * This package's own linked identity.
+ *
+ * It used to re-export core's decorators verbatim and declare `packageName`
+ * as a bare literal that nothing was bound to. The decorators therefore came
+ * from `corePackage`, so everything declared here registered under
+ * `@_linked/core`: this package's ontology landed in core's entry in the
+ * package tree, and the next shape added here would silently have been given a
+ * `.../shape/core/...` IRI. That IRI is persisted data and `Server.call`
+ * routes on the package name inside it, so a shape naming the wrong package is
+ * simply unreachable.
+ *
+ * No shape is decorated here today, so nothing was mis-registered — the cost
+ * was waiting for the first one. Same defect, same fix, as linked-fw/owl#26.
+ */
+export declare const linkedShape: {
+    <T extends typeof import("@_linked/core/shapes/Shape").Shape>(constructor: T): void;
+    <T extends typeof import("@_linked/core/shapes/Shape").Shape>(config?: import("@_linked/core/utils/Package").ShapeConfig): (constructor: T) => void;
+}, linkedUtil: (constructor: any) => any, linkedOntology: (allFileExports: any, nameSpace: (term: string) => import("@_linked/core/utils/NodeReference").NodeReferenceValue, suggestedPrefixAndFileName: string, loadDataFunction?: () => Promise<any>, dataSource?: string | string[]) => void, registerPackageExport: (exportedObject: any) => void, registerPackageModule: (_module: any) => void, getPackageShape: (name: string) => import("@_linked/core/shapes/Shape").ShapeConstructor | undefined, packageExports: any, packageName: string;

package/lib/esm/package.js

@@ -1,4 +1,18 @@
-import { getPackageShape, linkedOntology, linkedShape, linkedUtil, packageExports, registerPackageExport, registerPackageModule, } from '@_linked/core/package';
-export const { packageName } = { packageName: '@_linked/primitives' };
-export { getPackageShape, linkedOntology, linkedShape, linkedUtil, packageExports, registerPackageExport, registerPackageModule, };
+import { linkedPackage } from '@_linked/core/utils/Package';
+/**
+ * This package's own linked identity.
+ *
+ * It used to re-export core's decorators verbatim and declare `packageName`
+ * as a bare literal that nothing was bound to. The decorators therefore came
+ * from `corePackage`, so everything declared here registered under
+ * `@_linked/core`: this package's ontology landed in core's entry in the
+ * package tree, and the next shape added here would silently have been given a
+ * `.../shape/core/...` IRI. That IRI is persisted data and `Server.call`
+ * routes on the package name inside it, so a shape naming the wrong package is
+ * simply unreachable.
+ *
+ * No shape is decorated here today, so nothing was mis-registered — the cost
+ * was waiting for the first one. Same defect, same fix, as linked-fw/owl#26.
+ */
+export const { linkedShape, linkedUtil, linkedOntology, registerPackageExport, registerPackageModule, getPackageShape, packageExports, packageName, } = linkedPackage('@_linked/primitives');
 //# sourceMappingURL=package.js.map

package/lib/esm/package.js.map

@@ -1 +1 @@
-{"version":3,"file":"package.js","sourceRoot":"","sources":["../../src/package.ts"],"names":[],"mappings":"AAAA,OAAO,EACL,eAAe,EACf,cAAc,EACd,WAAW,EACX,UAAU,EACV,cAAc,EACd,qBAAqB,EACrB,qBAAqB,GACtB,MAAM,uBAAuB,CAAC;AAE/B,MAAM,CAAC,MAAM,EAAE,WAAW,EAAE,GAAG,EAAE,WAAW,EAAE,qBAAqB,EAAE,CAAC;AAEtE,OAAO,EACL,eAAe,EACf,cAAc,EACd,WAAW,EACX,UAAU,EACV,cAAc,EACd,qBAAqB,EACrB,qBAAqB,GACtB,CAAC"}
+{"version":3,"file":"package.js","sourceRoot":"","sources":["../../src/package.ts"],"names":[],"mappings":"AAAA,OAAO,EAAC,aAAa,EAAC,MAAM,6BAA6B,CAAC;AAE1D;;;;;;;;;;;;;;GAcG;AACH,MAAM,CAAC,MAAM,EACX,WAAW,EACX,UAAU,EACV,cAAc,EACd,qBAAqB,EACrB,qBAAqB,EACrB,eAAe,EACf,cAAc,EACd,WAAW,GACZ,GAAG,aAAa,CAAC,qBAAqB,CAAC,CAAC"}

package/lib/esm/package.json

@@ -10,7 +10,7 @@
     "type": "git",
     "url": "git+https://github.com/linked-fw/primitives.git"
   },
-  "version": "1.3.0",
+  "version": "1.3.2",
   "packageManager": "npm@11.19.1",
   "linkedPackage": true,
   "license": "ISC",

package/package.json

@@ -10,10 +10,11 @@
     "type": "git",
     "url": "git+https://github.com/linked-fw/primitives.git"
   },
-  "version": "1.3.0",
+  "version": "1.3.2",
   "packageManager": "npm@11.19.1",
   "linkedPackage": true,
   "main": "lib/cjs/index.js",
+  "types": "index.d.ts",
   "license": "ISC",
   "scripts": {
     "start": "npm exec linked dev",

package/test/package-identity.test.mjs

@@ -0,0 +1,28 @@
+import assert from 'node:assert/strict';
+import test from 'node:test';
+
+/**
+ * Which `linkedPackage()` the decorators come from decides the name everything
+ * in this package registers under — the ontology here today, and the IRI of the
+ * first `@linkedShape` anyone adds tomorrow. `src/package.ts` used to re-export
+ * core's decorators, so all of it landed under `@_linked/core`.
+ *
+ * The test is on object identity rather than on a registered IRI or a key in
+ * the global package tree, because both of those are core's own shapes and have
+ * changed across its versions — and CI resolves a different `@_linked/core`
+ * from the workspace does. `packageExports` *being* core's registry object is
+ * the defect itself, stated in the one form that holds on every version.
+ */
+
+test('this package does not share core\'s export registry', async () => {
+  const own = await import(new URL('../lib/esm/package.js', import.meta.url));
+  const core = await import('@_linked/core/package');
+
+  assert.notEqual(
+    own.packageExports,
+    core.packageExports,
+    'packageExports is core\'s registry: the decorators here are core\'s, so ' +
+      'everything declared in this package registers under @_linked/core',
+  );
+  assert.equal(own.packageName, '@_linked/primitives');
+});