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
Is your feature request related to a problem? Please describe.
It's not really a feature request. It's a hint that webpack-dev-server changed it's logging features with version 4.0.0.
Hence the proxy.conf.js that is delivered with the alfresco-content-app has stopped generating log outputs on the console.
Describe the solution you'd like
According to the second link the functionality was replaced by infrastructureLogging as described here: webpack logging
Would be nice, if you "reactive" proxy logging with this new method, because it's vital e.g. for finding CORS issues.
Describe alternatives you've considered
none
Additional context
none
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
It's not really a feature request. It's a hint that webpack-dev-server changed it's logging features with version 4.0.0.
Hence the proxy.conf.js that is delivered with the alfresco-content-app has stopped generating log outputs on the console.
The marked setting is now invalid.
Please see here
Gihub Angular
and here:
Release Info webpack.
Describe the solution you'd like
According to the second link the functionality was replaced by infrastructureLogging as described here:
webpack logging
Would be nice, if you "reactive" proxy logging with this new method, because it's vital e.g. for finding CORS issues.
Describe alternatives you've considered
none
Additional context
none
The text was updated successfully, but these errors were encountered: