bito-code-review[bot] commented on PR #43787:
URL: https://github.com/apache/superset/pull/43787#issuecomment-5504148466
<!-- Bito Reply -->
The issue flagged regarding Webpack runtime and manifest URLs becoming
relative is correct. In production builds, if `publicPath` is not explicitly
set or is set to an empty string, Webpack defaults to relative paths, which can
cause assets to be requested relative to the current route instead of the
intended static asset directory.
To resolve this, you should explicitly set the `publicPath` in your Webpack
configuration to the absolute path where your assets are hosted (e.g.,
`/static/assets/`).
Would you like me to fetch all other comments on this PR to validate and
propose fixes for them as well?
**superset-frontend/webpack.config.js**
```
output: {
publicPath: '/static/assets/',
// ... other output settings
}
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
