string | 'auto'In production mode, use this option to configure the URL prefix for static assets, such as a CDN URL.
assetPrefix affects the URLs of most static assets, including JavaScript files, CSS files, images, videos, etc. If an incorrect value is specified, you'll receive 404 errors while loading these resources.
This configuration is only used in production mode or none mode. In development mode, use dev.assetPrefix to configure the URL prefix.
Setting output.assetPrefix will add the value as a prefix to the URLs of all static assets like JavaScript, CSS, images, etc.
After the build, the URL of the JS bundle in the HTML file will be:
After the build, the URL of the JS bundle in the HTML file will be:
The default value of output.assetPrefix is the same as server.base.
When server.base is /foo, index.html and static assets can be accessed through http://localhost:3000/foo/.
It should be noted that when customizing the output.assetPrefix option, if you want static assets to be accessible normally during Rsbuild preview, output.assetPrefix should contain the same URL prefix as server.base. For example:
assetPrefix can be set to the following types of paths:
/assets/, or CDN paths like https://cdn.example.com/assets/../assets/.
It's not recommended to set assetPrefix as a relative path like './assets/'. This is because when assets are at different path depths, using relative paths may cause assets to load incorrectly.
publicPathThe functionality of output.assetPrefix is basically the same as the output.publicPath config in Rspack.
Key differences from the native configuration:
output.assetPrefix only takes effect in production mode.output.assetPrefix default value is the same as server.base.output.assetPrefix automatically appends a trailing / by default.output.assetPrefix is added to the process.env.ASSET_PREFIX environment variable (can only be accessed in client code).Use the __webpack_public_path__ variable provided by Rspack to dynamically set the URL prefix of static assets in JavaScript code.