craft.vite.asset no longer matches manifest format in Vite 3.x || 4.x

[Kashkin]

Describe the bug

I'm unable to reference static assets that are imported via JS and appear in the manifest, e.g. {{ craft.vite.asset("src/sprite.svg") }}.

Expected behaviour

The asset function should return the hashed path to assets in production. It appears the issue exists in extractAssetFiles in ManifestHelper.php, as it's looking for an assets key that doesn't exist in modern manifests.

Example Manifest

{
  "src/scripts/site-legacy.js": {
    "file": "assets/app-legacy-383a340e.js",
    "src": "src/scripts/site-legacy.js",
    "isEntry": true
  },
  "vite/legacy-polyfills-legacy": {
    "file": "assets/polyfills-legacy-e1be769e.js",
    "src": "vite/legacy-polyfills-legacy",
    "isEntry": true
  },
  "src/sprite.svg": {
    "file": "assets/sprite-dea648df.svg",
    "src": "src/sprite.svg"
  },
  "src/scripts/site.js": {
    "file": "assets/app-deed8d93.js",
    "src": "src/scripts/site.js",
    "isEntry": true
  }
}

Versions

• Plugin version: 4.0.4
• Craft version: 4.3.6.1
• Vite version: 4.0.4

[khalwat]

Looks like their docs may be out of date in terms of the manifest format: https://vitejs.dev/guide/backend-integration.html

[khalwat]

Relevant changes:

vitejs/vite#6649

vitejs/vite#8768

[khalwat]

Released a fix for this:

Craft 3: Version 1.0.30 -> https://github.com/nystudio107/craft-vite/releases/tag/1.0.30

Craft 4: Version 4.0.5 -> https://github.com/nystudio107/craft-vite/releases/tag/4.0.5