Feature Request: Allow Custom Server Config with Proxy Middleware Support in Static File Server Executor

[Squixx]

Feature Request: Allow Custom Server Config with Proxy Middleware Support in Static File Server Executor

Description

It would be very useful if the Nx static file server executor (file-server.impl.ts) supported an option to provide a custom server configuration file. This would allow users to set up their own server logic, including advanced proxying via middleware such as createProxyMiddleware, similar to what the Angular dev server supports.

Motivation and Use Case

Currently, the static file server only supports basic proxying via CLI options. In more complex scenarios—such as when you need to rewrite paths, add authentication, or handle advanced proxy logic—this is not sufficient. The Angular dev server allows users to provide a proxy.conf.json or custom middleware for flexible proxying. Bringing similar extensibility to the Nx static file server would enable more advanced and production-like local development setups.

Additionally, this feature would improve Nx Atomizer performance. It would allow for using static builds in scenarios where the Angular dev server is currently used only for its proxying capabilities. By enabling static file serving with custom proxy middleware, Atomizer can leverage faster static builds instead of relying on the Angular dev server as a proxy, resulting in improved speed and efficiency for affected workflows.

Proposed Solution

• Add an option (e.g., serverConfig or customServerPath) to the executor schema.
• If provided, the executor should load and use the custom server file, which can set up its own Express server, including custom proxy middleware via createProxyMiddleware.
• Document how to use this option and provide an example of a custom server that proxies API requests.

Example Use Case

A user wants to proxy /api requests to a backend server with custom headers and path rewrites, while serving static files for the rest. With this feature, they could provide a custom server file that uses createProxyMiddleware for /api and serves static files otherwise.

Benefits

• Parity with Angular dev server proxying capabilities.
• Enables advanced local development and testing scenarios.
• Greater flexibility for teams with complex backend integration needs.
• Improved Nx Atomizer performance by enabling static builds in proxy scenarios.

Additional Context

I am willing to implement this feature, but I would like to know if this is something that would be wanted before starting work.

See the current implementation in file-server.impl.ts for reference.