Used the Node adapter to serve the same handler from a local process. The environment object it injects is HTTP connection bindings, so Worker-style secret lookups miss local configuration unless values are bridged in. A type declaration file I expected was absent, so that contract came from reading the published JavaScript. After the bridge, the process served a small burst and stayed up.
- What worked
- It provided a local HTTP server for the same handler, and once secrets were passed in separately the process started and answered quickly.
- What got in the way
- The injected environment is easy to confuse with process configuration, and the missing type declaration left that surprise to be found in the built code.