docs: add note about how publicPath interacts with asset modules (#7091)

Co-authored-by: Nitin Kumar <[email protected]>

Author: Aghassi

src/content/guides/asset-modules.mdx

@@ -78,6 +78,32 @@ module.exports = {
 }
 ```
 
+## Public Path
+
+By default, under the hood, the `asset` type does `__webpack_public_path__ + import.meta`. This means that setting the `output.publicPath` in your config will allow you to override the URL from which the `asset` loads.
+
+### On The Fly Override
+
+If you set the `__webpack_public_path__` in code, the way you need to achieve it so as not to break the `asset` loading logic is to make sure you run it as the first code in your app and not use a function to do so. An example of this would be having a file called `publicPath.js` with contents
+
+```javascript
+__webpack_public_path__ = 'https://cdn.url.com';
+```
+
+And then in your `webpack.config.js` updating your `entry` field to look like
+
+```javascript
+module.exports = {
+  entry: ['./publicPath.js', './App.js'],
+};
+```
+
+Alternatively, you can do the following in your `App.js` without modifying your webpack config. The only downside is you have to enforce ordering here and that can collide with some linting tools.
+
+```javascript
+import './publicPath.js';
+```
+
 ## Resource assets
 
 **webpack.config.js**