StackBlitz WebContainers and External API Interoperability

StackBlitz WebContainers utilize a WebAssembly-based runtime to emulate a Node.js environment directly within the browser. This architecture allows for local execution of npm install and npm start without a remote backend, relying on a virtualized file system and shared memory buffers.

When integrating a WebContainer-based project with external REST APIs or third-party services, the runtime operates under the security constraints of the client's browser. This introduces specific boundaries regarding network request handling and header manipulation that differ from a standard server-side Node.js environment.

Given that the environment is subject to browser CORS restrictions, there is uncertainty regarding the most effective way to handle requests to endpoints that do not support the required headers without utilizing an external proxy.

• Does the WebContainer runtime provide a built-in mechanism to bypass CORS restrictions for development purposes?
• What is the recommended approach for simulating server-to-server authentication when the request originates from a browser-based WebAssembly sandbox?