Sign In

@expofp/schema

Package Overview
Dependencies
Maintainers
6
Versions
24
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

@expofp/schema - npm Package Compare versions

Comparing version
3.19.0
to
3.20.0
+13
-0
dist/lib/config.js

@@ -253,2 +253,15 @@ import * as z from 'zod';

legacyDataUrlBase: z.string().optional(),
/**
* Pin of the legacy data revision — the `version.json` value at manifest
* generation time. `loadConfig` cache-busts the legacy file refs with it
* (`?v=<pin>`) and skips its own `version.json` probe, so the manifest and
* the data it points at stay consistent by construction. `null` states
* "probed: no version.json exists" — the runtime cache-busts per load with
* a timestamp, still without probing. Only an ABSENT field (legacy
* manifests, which predate the pin) leaves the runtime to probe; the
* retired `$ref`-pointer shape still parses but is treated as absent. An
* input consumed by `loadConfig` like `legacyDataUrlBase`, never carried on
* the effective config.
*/
legacyDataVersion: z.union([z.string(), z.null(), z.object({ $ref: z.string() })]).optional(),
});

@@ -255,0 +268,0 @@ /**

+2
-2
{
"name": "@expofp/schema",
"version": "3.19.0",
"version": "3.20.0",
"type": "module",

@@ -28,3 +28,3 @@ "description": "ExpoFP SDK internal: expo data schemas and types",

"devDependencies": {
"@expofp/utils": "3.19.0"
"@expofp/utils": "3.20.0"
},

@@ -31,0 +31,0 @@ "files": [

Sorry, the diff of this file is too big to display