From 98061cc8184b600e070932ea19d30c8eb7be1951 Mon Sep 17 00:00:00 2001 From: Graham Campbell Date: Fri, 12 Jun 2026 21:14:48 +0100 Subject: [PATCH] Document scope of Proxy-backed file address resolution --- docs/guides/variables.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/guides/variables.md b/docs/guides/variables.md index 295c34303..d1c7324a0 100644 --- a/docs/guides/variables.md +++ b/docs/guides/variables.md @@ -497,7 +497,7 @@ functions: - schedule: ${file(./scheduleConfig.js):rate} # Reference a specific module ``` -Address resolution follows the value's own properties. If a JS file exports (or its resolver function returns) a `Proxy`-backed object, address segments are resolved through the proxy's `get` handler instead. The keys `__proto__`, `prototype` and `constructor` are only followed when they are own properties of the value, so an address can never traverse into prototype internals. +Address resolution follows the value's own properties. If a JS file exports (or its resolver function returns) a `Proxy`-backed object, address segments are resolved through the proxy's `get` handler instead. The keys `__proto__`, `prototype` and `constructor` are only followed when they are own properties of the value, so an address can never traverse into prototype internals. This proxy-aware resolution applies to `file(...)` addresses only — when the same value is reached another way (for example via a `${self:...}` reference into a property that was populated from a `${file(...)}` variable, or via `serverless print --path`), only own properties are followed. ### Exporting a function