fix: support asset importing (ssr)

[pi0]

template:

<img src="../assets/logo.svg">

 ERROR  [vite]: Rollup failed to resolve import "assets/logo.svg" from "pages/index.vue?vue&type=template&lang.js".                                                                     22:44:25
This is most likely unintended because it can break your application at runtime.
If you do want to externalize this module explicitly add it to
`build.rollupOptions.external`


 ERROR  Server compiled with errors: [vite]: Rollup failed to resolve import "assets/logo.svg" from "pages/index.vue?vue&type=template&lang.js".                                        22:44:25
This is most likely unintended because it can break your application at runtime.
If you do want to externalize this module explicitly add it to
`build.rollupOptions.external`

[pi0]

most of issues resolved with latest version of vite-plugin-vue. But URL generated by SSR is 404. (PR to track: #39)

[WebMBX]

same error, still not working...

nuxt: 2.15.2
nuxt-vite: 0.0.28

<img src="logo.svg"/>

ERROR [vite]: Rollup failed to resolve import "logo.svg" from "components/Head.vue?vue&type=template&lang.js". This is most likely unintended because it can break your application at runtime. If you do want to externalize this module explicitly add it tobuild.rollupOptions.external``

[jshimkoski]

Any status on this? I'd love to jump on the Vite train but the inability to use assets from the static directory is a showstopper.

I'm surprised the content module is marked as working with Vite as its assets are basically required to be served from the static directory.

[RobbieTheWagner]

Just ran into this as well. Any updates here?

[togetherwithasteria]

Same issue here, running on Nuxt Vite 0.0.37.

For workarounds, I guess using third-party CDN would work.

[productdevbook]

v1.0.0

[pi0]

@productfrontenddeveloper Would you please make a reproduction or share index.vue?

[productdevbook]

@productfrontenddeveloper Would you please make a reproduction or share index.vue?

index.vue.zip

[RobbieTheWagner]

@pi0 I see you merged a PR to disable SSR in development. Won't that introduce a lot of gotchas if the dev environment does not support SSR?

[pi0]

Yes, you have to be careful about SSR compatibility during development. Due to issues like this and others mentioned in #139, disabling allows having a more stable experience of vite. Hopefully, we can turn SSR back to enabled soon :)

[productdevbook]

when fixed :(

[ahmed56734]

import like this with @ <img src="@/assets/logo.svg">