publicPath not working when using full URI

[bokub]

Hi,

In a Nuxt app, for some reason, I need all my assets URIs to include the domain.

For example, in the rendered HTML, instead of having

<script src="/_nuxt/286f58c.js">

I would like to have something like:

<script src="https://mysite.vercel.app/_nuxt/286f58c.js">

or <script src="https://mysite.vercel.app/assets/286f58c.js">

---

According to the Nuxt doc, I can use the publicPath option for that.

So I tried this config:

  build: {
    publicPath: 'https://mysite.vercel.app/assets/',
  },

And the generated HTML looks good:

<script src="https://mysite.vercel.app/assets/7155d93.js" defer></script>

However, the assets don't exist in the output, and there is a weird empty https: folder instead:

With the following config, the problem is exactly the same, no assets in the output...

  build: {
    publicPath: 'https://mysite.vercel.app/_nuxt/',
  },

Can you confirm that it's a bug and not some misunderstanding from my side?

Thanks a lot 👍

[danielroe]

@bokub What you would normally do is:

1. set publicPath as you've done above, to a CDN
2. build/generate your app
3. (if building) upload your .nuxt/dist/client folder to that location on your CDN
4. (if generating) upload the contents of your dist folder to that location on your CDN

However, yes - it was broken because vercel-builder assumed publicPath would be a directory. Should now be fixed in 0.21.3 but note that you will need to set your publicPath to 'https://mysite.vercel.app/_nuxt/' rather than a custom directory.

[bokub]

Wow, that was fast, and it's working perfectly!

Thanks a lot 👍