fix: workaround Date heuristics

Author: pieh

src/run/handlers/cache.cts

@@ -55,7 +55,7 @@ export class NetlifyCacheHandler implements CacheHandlerForMultipleVersions {
 
       if (typeof revalidate === 'number') {
         const revalidateAfter = revalidate * 1_000 + blob.lastModified
-        return (revalidateAfter - Date.now()) / 1_000
+        return (revalidateAfter - DateBeforeNextPatchedIt.now()) / 1_000
       }
       if (revalidate === false) {
         return 'PERMANENT'
@@ -441,7 +441,7 @@ export class NetlifyCacheHandler implements CacheHandlerForMultipleVersions {
   async set(...args: Parameters<CacheHandlerForMultipleVersions['set']>) {
     return this.tracer.withActiveSpan('set cache key', async (span) => {
       const [key, data, context] = args
-      const lastModified = Date.now()
+      const lastModified = DateBeforeNextPatchedIt.now()
       span.setAttributes({ key, lastModified })
 
       getLogger().debug(`[NetlifyCacheHandler.set]: ${key}`)

src/run/handlers/server.ts

@@ -22,6 +22,7 @@ import { configureUseCacheHandlers } from './use-cache-handler.js'
 import { setupWaitUntil } from './wait-until.cjs'
 // make use of global fetch before Next.js applies any patching
 setFetchBeforeNextPatchedIt(globalThis.fetch)
+globalThis.DateBeforeNextPatchedIt = Date
 // configure globals that Next.js make use of before we start importing any Next.js code
 // as some globals are consumed at import time
 const { nextConfig: initialNextConfig, enableUseCacheHandler } = await getRunConfig()
@@ -35,6 +36,30 @@ const nextImportPromise = import('../next.cjs')
 
 let nextHandler: WorkerRequestHandler
 
+// Lambda Runtime patches these methods to include timestamp with `new Date()` which ...
+// has tension with https://nextjs.org/docs/messages/next-prerender-current-time
+// as this timestamp is NOT impacting Next.js render we temporarily restore original Date
+// to not affect Next.js heuristics related to `Date` usage
+for (const consoleMethod of [
+  'trace',
+  'debug',
+  'info',
+  'log',
+  'warn',
+  'error',
+  // fatal is not console method, but AWS Lambda Runtime adds it
+  'fatal',
+] as const) {
+  const originalMethod = console[consoleMethod].bind(console)
+  console[consoleMethod] = (...args: unknown[]) => {
+    const patchedDate = Date
+    Date = DateBeforeNextPatchedIt
+    const retval = originalMethod(...args)
+    Date = patchedDate
+    return retval
+  }
+}
+
 /**
  * When Next.js proxies requests externally, it writes the response back as-is.
  * In some cases, this includes Transfer-Encoding: chunked.

src/run/handlers/tags-handler.cts

@@ -130,7 +130,7 @@ async function doRevalidateTagAndPurgeEdgeCache(tags: string[]): Promise<void> {
   }
 
   const tagManifest: TagManifest = {
-    revalidatedAt: Date.now(),
+    revalidatedAt: DateBeforeNextPatchedIt.now(),
   }
 
   const cacheStore = getMemoizedKeyValueStoreBackedByRegionalBlobStore({ consistency: 'strong' })

src/run/handlers/use-cache-handler.ts

@@ -112,7 +112,8 @@ export const NetlifyDefaultUseCacheHandler = {
         }
 
         const { entry } = privateEntry
-        const ttl = (entry.timestamp + entry.revalidate * 1000 - Date.now()) / 1000
+        const ttl =
+          (entry.timestamp + entry.revalidate * 1000 - DateBeforeNextPatchedIt.now()) / 1000
         if (ttl < 0) {
           // In-memory caches should expire after revalidate time because it is
           // unlikely that a new entry will be able to be used before it is dropped

src/run/headers.ts

@@ -192,7 +192,7 @@ export const adjustDateHeader = async ({
     return
   }
 
-  const lastModifiedDate = new Date(lastModified)
+  const lastModifiedDate = new DateBeforeNextPatchedIt(lastModified)
   // Show actual date of the function call in the date header
   headers.set('x-nextjs-date', headers.get('date') ?? lastModifiedDate.toUTCString())
   // Setting Age also would work, but we already have the lastModified time so will use that.