bevy0.16.0-rc.1 build to wasm, runing can not load asset

[cherish-ltt]

when bevy project build to wasm32-unknown-unknown
then, npm run dev
log:

but in network , png load http-status:200

Is it because specific configurations are needed for WASM? How should I solve it

[cherish-ltt]

I found a .meta request below the network. What is this and is it because of this error

[cherish-ltt]

After I changed WebGL2 to WebGPU, the log showed that it supports a maximum of 8 textures, but 12 were loaded

[copygirl]

My uneducated guess, looking at one of your comments, is that your webserver is not serving .meta files correctly.

[cherish-ltt]

But I don't know what the .meta file is. Will it be generated by the Vue project itself? My bevy assets folder only has .png source files

[mockersf]

your npm run dev command start a dev server configured for single page applications. every URL not found is replaced by the index.html file.
Bevy expects to get 404 errors for meta fails not found, but your dev server return a 200 status with html. Bevy fails to deserialise the meta file as its content is html instead of the expected content.

You can either fix your dev server to return 404 error for .meta files, or configure Bevy to not look for .meta files if you don't need them

To configure Bevy, when you add the DefaultPlugins to your app, do:

DefaultPlugins
    .set(AssetPlugin {
        // Wasm builds will check for meta files (that don't exist) if this isn't set.
        // This causes errors and even panics on web build on itch or with SPA dev-servers.
        // See https://github.com/bevyengine/bevy_github_ci_template/issues/48.
        meta_check: AssetMetaCheck::Never,
        ..default()
    })

[cherish-ltt]

As you said, I modified the configuration of the Vue project to return http404, and the wasm packaged by Bevy ran normally

[cherish-ltt]

Thank you very much