@cloudbitmaps/core 0.23.0 → 0.24.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -9,15 +9,6 @@ pnpm add @cloudbitmaps/roaring @cloudbitmaps/s3 # the store, and the storage y
9
9
 
10
10
  Install the same version of every `@cloudbitmaps/*` package: they release together, and each pins the exact version of `core` it was built with.
11
11
 
12
- `roaring` needs its one install script to fetch its native binary, and newer clients run a dependency's script only if you allow it. Allow it before you install:
13
-
14
- - **npm 12:** add `{ "allowScripts": { "roaring": true } }` to your `package.json`. Without it the install exits 0 and the package throws at `import`. npm 11 runs the script but warns until you allow it the same way.
15
- - **pnpm 11 and later:** put `allowBuilds: { roaring: true }` in a `pnpm-workspace.yaml` beside your `package.json`. Those versions no longer read the `package.json` `pnpm` key. Without it the install exits 1 with `ERR_PNPM_IGNORED_BUILDS`.
16
- - **pnpm 10:** add `{ "pnpm": { "onlyBuiltDependencies": ["roaring"] } }` to your `package.json`. Without it the install exits 0 and the package throws at `import`.
17
- - **pnpm 9:** nothing extra.
18
-
19
- [Details](https://github.com/cloudbitmaps/cloudbitmaps/blob/main/docs/guide/getting-started.md#cannot-find-module-buildreleaseroaringnode-after-a-successful-install).
20
-
21
12
  Depend on `@cloudbitmaps/core` directly only to write a driver, through `@cloudbitmaps/core/driver-kit`.
22
13
 
23
14
  > **The main entry of this package, and `@cloudbitmaps/core/node`, are internal.** The main entry is the engine `@cloudbitmaps/roaring` and the driver packages are built on, and `/node` holds the backends and keystore that need a Node builtin. Both are outside the stability promise: they can change in any minor release, and a change to either gets no CHANGELOG Breaking entry. Install `@cloudbitmaps/roaring` and a driver. The public entry here is `@cloudbitmaps/core/driver-kit`, the contract for writing a driver.
@@ -1193,6 +1193,10 @@ function rollbackKnown(prev, target) {
1193
1193
  if (!inserted && moved.length <= MAX_KNOWN_GENERATIONS) return moved;
1194
1194
  return capInsert(moved, /* @__PURE__ */ new Set([target.generation, prev.currentGen]), leasedByRow(prev));
1195
1195
  }
1196
+ function sameKnownGens(a, b) {
1197
+ if (a === void 0 || b === void 0) return a === b;
1198
+ return a.length === b.length && a.every((e, i) => e.generation === b[i].generation && e.footerCrc === b[i].footerCrc);
1199
+ }
1196
1200
  function pruneKnown(record, doomed) {
1197
1201
  const found = usableKnownGens(record);
1198
1202
  if (found === void 0) return void 0;
@@ -1361,10 +1365,11 @@ export {
1361
1365
  keptWindow,
1362
1366
  nextKnown,
1363
1367
  rollbackKnown,
1368
+ sameKnownGens,
1364
1369
  pruneKnown,
1365
1370
  describingKnown,
1366
1371
  isFullLedger,
1367
1372
  fallbackBound,
1368
1373
  knownGensShapeFault
1369
1374
  };
1370
- //# sourceMappingURL=chunk-MVUD4R72.js.map
1375
+ //# sourceMappingURL=chunk-2B2QF4FU.js.map