Relative asset plugin broken

[liaoyu1992]

Environment

window10
nodejs: v16.14.0

Reproduction

GET http://localhost:3000/main-62bdb63b.mjs net::ERR_ABORTED 404 (Page not found: /main-62bdb63b.mjs)
GET http://localhost:3000/main.4f570753.css net::ERR_ABORTED 404 (Page not found: /main.4f570753.css)
entry-dfffb6f1.mjs:8 Event {isTrusted: true, type: 'error', target: link, currentTarget: link, eventPhase: 2, …}
Uncaught (in promise) Event {isTrusted: true, type: 'error', target: link, currentTarget: null, eventPhase: 0, …}

Describe the bug

When I'm routing to a certain page,for example:
router.push({ name: 'main'}),
then report the above error

Additional context

No response

Logs

No response

[phanmn]

Seeing this issue also

[phanmn]

• In normal entry file (entry-xxxxxx.mjs)

• In bug entry file ((entry-xxxxxx.mjs)

[danielroe]

Would you provide a reproduction? 🙏

[oritwoen]

@danielroe please check also unocss/unocss#676 the error looks similar

[dualmacops]

I have the same problem, but it looks like it only happens on the / route, not in the others

[Denoder]

seems to happen on this commit precisely: nuxt/framework@a0f8a44

[hi-reeve]

got the same issues in preview mode but not with the route but with the component

[xiao-e-yun]

hashes match is true
but miss buildAssetsDir or _nuxt/ ( cdnURL work

[peteromano]

Same.

Doesn't look like hashes in my case; column (a layout), is loaded correctly initially then attempted to load again under the root (not _nuxt).. Also, not sure why the entire app is completely broken from this.

[peteromano]

is there a workaround for now or proposed fix to wait on?

[Denoder]

@peteromano for now you can use 3.0.0-27434608.0c99002 as the nuxt3 version until it's fixed

[xiao-e-yun]

This is my temporary solution
it may not be the best but it works

node ./deploy.mjs

~/deploy.mjs

import fs from 'node:fs/promises';
import path from 'node:path';

const p = "/_nuxt/"

const __dirname = new URL(".",import.meta.url).pathname
const from = path.resolve(__dirname,".output/public"+p)

try {
  let files = await fs.readdir(from)
  files = files.filter(v=>v.startsWith("entry-") && v.endsWith(".mjs"))

  if (files.length) {
    const file = path.resolve(from,files[0])
    let data = await fs.readFile(file,{encoding:"utf-8"})

    const replace = []
    const regex = /import\("(.*?)\.mjs"\)/gm
    let match = undefined

    data = data.replaceAll("./","")

    for (;;) {
      match = regex.exec(data)
      if(match===null) break
      replace.push(match[1])
    }

    replace.forEach(v=>{
      const css = new RegExp(v.slice(0,v.indexOf("-"))+"\.(.{8})\.css")
      data = data.replaceAll(v+".mjs",path.resolve(p,v+".mjs"))
      data = data.replace(css,p+"$&")
    })
    await fs.writeFile(file,data)
  }
} catch(e) {
  console.error(e)
}

[lukeocodes]

@peteromano for now you can use 3.0.0-27434608.0c99002 as the nuxt3 version until it's fixed

This release did resolve it for me for now.

  "devDependencies": {
    "nuxt3": "3.0.0-27434608.0c99002",
  }

[bmhtech07]

@peteromano for now you can use 3.0.0-27434608.0c99002 as the nuxt3 version until it's fixed

This worked for me. Thanks!

[danielroe]

@bmhtech07 This bug should not be present in the current version of Nuxt. If it is, would you open a new issue with a reproduction?

[bmhtech07]

False alarm. Staging branch hadn't been updated! Now fine!

[ennioVisco]

@bmhtech07 This bug should not be present in the current version of Nuxt. If it is, would you open a new issue with a reproduction?

@danielroe it seems to be present again in 3.0.0-27480376.fdd38f9. Rolling back to that commit solves it

[danielroe]

@ennioVisco Would you open a new issue with a reproduction?