You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using a custom Webpack configuration with Angular 17, the proxy configuration does not work as expected. The proxy setup defined in the angular.json file is not routing API requests as intended [even if provided using --proxy-config cli command) and throws 404 error/CORS issues. This issue is occurring despite the correct proxy settings being defined in the proxy.conf.json file and the angular.json configuration pointing to the custom Webpack configuration.
Minimal Reproduction
Steps to Reproduce:
Create an Angular 17 project using the Angular CLI.
Install the necessary dependencies for using a custom Webpack configuration (e.g., @angular-builders/custom-webpack).
Configure a custom Webpack configuration (webpack.config.ts) as per the project’s requirements.
Define a proxy configuration in a proxy.conf.json file, specifying API routes and targets.
In the angular.json file, update the build and serve configurations to use the custom Webpack configuration.
`
Hi, I am assuming you tried it without the custom webpack config and it worked?
We're gonna need a repo with minimal reproduction in order to address this issue.
Describe the Bug
When using a custom Webpack configuration with Angular 17, the proxy configuration does not work as expected. The proxy setup defined in the angular.json file is not routing API requests as intended [even if provided using --proxy-config cli command) and throws 404 error/CORS issues. This issue is occurring despite the correct proxy settings being defined in the proxy.conf.json file and the angular.json configuration pointing to the custom Webpack configuration.
Minimal Reproduction
Steps to Reproduce:
In the angular.json file, update the build and serve configurations to use the custom Webpack configuration.
`
Proxy config example file.
** webpack config file **
Expected Behavior
Proxy config should work as expected.
Environment
The text was updated successfully, but these errors were encountered: