# Automatic publicPath is not supported in this browser

**URL:** https://discourse.roots.io/t/automatic-publicpath-is-not-supported-in-this-browser/22619
**Category:** sage
**Tags:** bud, sage10
**Created:** 2022-03-18T02:55:00Z
**Posts:** 13
**Showing post:** 11 of 13

## Post 11 by @kellymears — 2022-03-23T02:32:05Z

We think we might have a solution to get publicPath to play nice between acorn and bud.

In the meantime, you have two options:

1. Probably best one. Set the `publicPath` specifically in the client using the [`EntryDescription` object](https://webpack.js.org/concepts/entry-points/#entrydescription-object)

> **[Entry Points | webpack](https://webpack.js.org/concepts/entry-points/#entrydescription-object)**
>
> webpack is a module bundler. Its main purpose is to bundle JavaScript files for usage in a browser, yet it is also capable of transforming, bundling, or packaging just about any resource or asset.

Example:

```
bud.entry({
  app: {
    import: ['app.js']
    publicPath: '/app/themes/sage/public/'
  }
})
```

1. Another option is to set ` __webpack_public_path__ ` at the top of your entrypoint. See the webpack docs for the concept:

> **[Public Path | webpack](https://webpack.js.org/guides/public-path/#on-the-fly)**
>
> webpack is a module bundler. Its main purpose is to bundle JavaScript files for usage in a browser, yet it is also capable of transforming, bundling, or packaging just about any resource or asset.

If you want to set it up with `DefinePlugin` as documented you can utilize `bud.define`

> **[bud.define | bud.js](https://bud.js.org/docs/bud.define/)**
>
> Replace variables in your application code and templates at compile time.

---

_[View the full topic](https://discourse.roots.io/t/automatic-publicpath-is-not-supported-in-this-browser/22619)._