@rebasepro/types 0.25.0-canary.ge06257e → 0.25.1

package/dist/types/content_hash.d.ts

@@ -0,0 +1,20 @@
+/**
+ * Whether a static build's file name carries a content hash: the files the
+ * runtime serves `immutable` for a year, and the ones `rebase build` writes
+ * `.br` and `.gz` beside. One rule for both, so a file is never precompressed
+ * and revalidated, or cached for a year and compressed on every request.
+ *
+ * Two shapes count:
+ *
+ * - **Vite's own**, `[name]-[hash]`: the last eight characters of the name,
+ *   after a `-`. They are base64url, an alphabet with `-` and `_` in it, so
+ *   about one hash in eight holds a `-` (`index-C-WpENHZ.js`,
+ *   `page10-D6Dq--fD.js`), and the last `-` is not where it starts.
+ * - **A longer one** with no `-` in it, eight characters or more after the last
+ *   `-` (`[hash:12]`, another bundler's names).
+ *
+ * Either must hold a digit or a capital. That is the evidence of a hash: a
+ * hand-written `vendor-analytics.js` is not taken for one, and gets revalidated
+ * rather than pinned in every visitor's cache with no way to recall it.
+ */
+export declare function isContentHashedFileName(fileName: string): boolean;

package/dist/types/index.d.ts

@@ -32,6 +32,7 @@ export * from "./scopes.js";
 export * from "./history.js";
 export * from "./postgres_introspection.js";
 export * from "./project_manifest.js";
+export * from "./content_hash.js";
 export * from "./collection_contract.js";
 export * from "./schema_version.js";
 export * from "./storage_authorize.js";

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@rebasepro/types",
-  "version": "0.25.0-canary.ge06257e",
+  "version": "0.25.1",
   "description": "Rebase type definitions — shared interfaces and controller types",
   "keywords": [
     "rebase",