.

node_modules/next/dist/esm/shared/lib/segment-cache/segment-value-encoding.js

@@ -0,0 +1,65 @@
+import { PAGE_SEGMENT_KEY } from '../segment';
+export const ROOT_SEGMENT_REQUEST_KEY = '';
+export const HEAD_REQUEST_KEY = '/_head';
+export function createSegmentRequestKeyPart(segment) {
+    if (typeof segment === 'string') {
+        if (segment.startsWith(PAGE_SEGMENT_KEY)) {
+            // The Flight Router State type sometimes includes the search params in
+            // the page segment. However, the Segment Cache tracks this as a separate
+            // key. So, we strip the search params here, and then add them back when
+            // the cache entry is turned back into a FlightRouterState. This is an
+            // unfortunate consequence of the FlightRouteState being used both as a
+            // transport type and as a cache key; we'll address this once more of the
+            // Segment Cache implementation has settled.
+            // TODO: We should hoist the search params out of the FlightRouterState
+            // type entirely, This is our plan for dynamic route params, too.
+            return PAGE_SEGMENT_KEY;
+        }
+        const safeName = // TODO: FlightRouterState encodes Not Found routes as "/_not-found".
+        // But params typically don't include the leading slash. We should use
+        // a different encoding to avoid this special case.
+        segment === '/_not-found' ? '_not-found' : encodeToFilesystemAndURLSafeString(segment);
+        // Since this is not a dynamic segment, it's fully encoded. It does not
+        // need to be "hydrated" with a param value.
+        return safeName;
+    }
+    const name = segment[0];
+    const paramType = segment[2];
+    const safeName = encodeToFilesystemAndURLSafeString(name);
+    const encodedName = '$' + paramType + '$' + safeName;
+    return encodedName;
+}
+export function appendSegmentRequestKeyPart(parentRequestKey, parallelRouteKey, childRequestKeyPart) {
+    // Aside from being filesystem safe, segment keys are also designed so that
+    // each segment and parallel route creates its own subdirectory. Roughly in
+    // the same shape as the source app directory. This is mostly just for easier
+    // debugging (you can open up the build folder and navigate the output); if
+    // we wanted to do we could just use a flat structure.
+    // Omit the parallel route key for children, since this is the most
+    // common case. Saves some bytes (and it's what the app directory does).
+    const slotKey = parallelRouteKey === 'children' ? childRequestKeyPart : `@${encodeToFilesystemAndURLSafeString(parallelRouteKey)}/${childRequestKeyPart}`;
+    return parentRequestKey + '/' + slotKey;
+}
+// Define a regex pattern to match the most common characters found in a route
+// param. It excludes anything that might not be cross-platform filesystem
+// compatible, like |. It does not need to be precise because the fallback is to
+// just base64url-encode the whole parameter, which is fine; we just don't do it
+// by default for compactness, and for easier debugging.
+const simpleParamValueRegex = /^[a-zA-Z0-9\-_@]+$/;
+function encodeToFilesystemAndURLSafeString(value) {
+    if (simpleParamValueRegex.test(value)) {
+        return value;
+    }
+    // If there are any unsafe characters, base64url-encode the entire value.
+    // We also add a ! prefix so it doesn't collide with the simple case.
+    const base64url = btoa(value).replace(/\+/g, '-') // Replace '+' with '-'
+    .replace(/\//g, '_') // Replace '/' with '_'
+    .replace(/=+$/, '') // Remove trailing '='
+    ;
+    return '!' + base64url;
+}
+export function convertSegmentPathToStaticExportFilename(segmentPath) {
+    return `__next${segmentPath.replace(/\//g, '.')}.txt`;
+}
+
+//# sourceMappingURL=segment-value-encoding.js.map

node_modules/next/dist/esm/shared/lib/segment-cache/vary-params-decoding.js

@@ -0,0 +1,32 @@
+/**
+ * Vary Params Decoding
+ *
+ * This module is shared between server and client.
+ */ /**
+ * Synchronously reads vary params from a thenable.
+ *
+ * By the time this is called (client-side or in collectSegmentData), the
+ * thenable should already be fulfilled because the Flight stream has been
+ * fully received. We check the status synchronously to avoid unnecessary
+ * microtasks.
+ *
+ * Returns null if the thenable is still pending (which shouldn't happen in
+ * normal operation - it indicates the server failed to track vary params).
+ */ export function readVaryParams(thenable) {
+    // Attach a no-op listener to force Flight to synchronously resolve the
+    // thenable. When a thenable arrives from the Flight stream, it may be in an
+    // intermediate 'resolved_model' state (data received but not unwrapped).
+    // Calling .then() triggers Flight to transition it to 'fulfilled', making
+    // the value available synchronously. React uses this same optimization
+    // internally to avoid unnecessary microtasks.
+    thenable.then(noop);
+    // If the thenable is still not 'fulfilled' after calling .then(), the server
+    // failed to resolve it before the stream ended. Treat as unknown.
+    if (thenable.status !== 'fulfilled') {
+        return null;
+    }
+    return thenable.value;
+}
+const noop = ()=>{};
+
+//# sourceMappingURL=vary-params-decoding.js.map

node_modules/next/dist/esm/shared/lib/segment-cache/vary-params-decoding.js.map

@@ -0,0 +1 @@
+{"version":3,"sources":["../../../../../src/shared/lib/segment-cache/vary-params-decoding.ts"],"sourcesContent":["/**\n * Vary Params Decoding\n *\n * This module is shared between server and client.\n */\n\nexport type VaryParams = Set<string>\n\ntype FulfilledVaryParamsThenable = {\n  status: 'fulfilled'\n  value: VaryParams\n} & PromiseLike<VaryParams>\n\ntype PendingVaryParamsThenable = {\n  // 'resolved_model' is an internal React Flight state: the underlying model\n  // data has arrived but the thenable hasn't been \"unwrapped\" yet. Calling\n  // .then() triggers Flight to synchronously transition to 'fulfilled'.\n  status: 'pending' | 'resolved_model'\n  value: unknown\n} & PromiseLike<VaryParams>\n\nexport type VaryParamsThenable =\n  | FulfilledVaryParamsThenable\n  | PendingVaryParamsThenable\n\n/**\n * Synchronously reads vary params from a thenable.\n *\n * By the time this is called (client-side or in collectSegmentData), the\n * thenable should already be fulfilled because the Flight stream has been\n * fully received. We check the status synchronously to avoid unnecessary\n * microtasks.\n *\n * Returns null if the thenable is still pending (which shouldn't happen in\n * normal operation - it indicates the server failed to track vary params).\n */\nexport function readVaryParams(\n  thenable: VaryParamsThenable\n): VaryParams | null {\n  // Attach a no-op listener to force Flight to synchronously resolve the\n  // thenable. When a thenable arrives from the Flight stream, it may be in an\n  // intermediate 'resolved_model' state (data received but not unwrapped).\n  // Calling .then() triggers Flight to transition it to 'fulfilled', making\n  // the value available synchronously. React uses this same optimization\n  // internally to avoid unnecessary microtasks.\n  thenable.then(noop)\n  // If the thenable is still not 'fulfilled' after calling .then(), the server\n  // failed to resolve it before the stream ended. Treat as unknown.\n  if (thenable.status !== 'fulfilled') {\n    return null\n  }\n  return thenable.value\n}\n\nconst noop = () => {}\n"],"names":["readVaryParams","thenable","then","noop","status","value"],"mappings":"AAAA;;;;CAIC,GAqBD;;;;;;;;;;CAUC,GACD,OAAO,SAASA,eACdC,QAA4B;IAE5B,uEAAuE;IACvE,4EAA4E;IAC5E,yEAAyE;IACzE,0EAA0E;IAC1E,uEAAuE;IACvE,8CAA8C;IAC9CA,SAASC,IAAI,CAACC;IACd,6EAA6E;IAC7E,kEAAkE;IAClE,IAAIF,SAASG,MAAM,KAAK,aAAa;QACnC,OAAO;IACT;IACA,OAAOH,SAASI,KAAK;AACvB;AAEA,MAAMF,OAAO,KAAO","ignoreList":[0]}