assets not resolve with ~ symbol

[elselapatha]

assets images not resolve after upgrade to quasar 1.4.5 and app 1.3.0
inspect the source and code is show like <img src="[object Module]" style="width: 30vw; max-width: 150px;">

[ggeorgiev92]

I have the same issue. Issue occur when quasar/app is 1.3.0 version (maybe some of updated dependencies). I downgrade my app to last stable 1.2.4 and everything work like a charm.

[jacksongross]

I think it could be related to #5621

[0xDarker]

+1

[elselapatha]

I have the same issue. Issue occur when quasar/app is 1.3.0 version (maybe some of updated dependencies). I downgrade my app to last stable 1.2.4 and everything work like a charm.

Thanks. Solve the issue. but this is workaround.

[miladmeidanshahi]

the same problem please update @rstoenescu

[pdanpdan]

Can you please check file-loader's version on working and not working app (1.2.4 and 1.3.0) with npm list file-loader and report back?

[rstoenescu]

Hi,

Thanks for reporting! Fixed in "@quasar/app" v1.3.1. Please upgrade to it.

[0xDarker]

I upgrade to "@quasar/app" v1.3.1 but this issue still exists. @rstoenescu

[rstoenescu]

@0xDarker it's impossible. make a cleanup of node_modules and yarn.lock/package-lock.json and yarn/npm install again. Also make sure that you haven't manually added url-loader or file-loader to your project.

[0xDarker]

@0xDarker it's impossible. make a cleanup of node_modules and yarn.lock/package-lock.json and yarn/npm install again. Also make sure that you haven't manually added url-loader or file-loader to your project.

Sorry it ’s really because I added file-loader, thanks

[rstoenescu]

No prob. Glad it's working for you too now.

[Propaganistas]

I deleted node_modules and yarn.lock, I don't have file-loader / url-loader specified and yet I'm still experiencing this issue from v1.3.1 and onwards.

[rstoenescu]

@Propaganistas this has been fixed 101%. are you sure that you are running latest q/app? what does it say when you run quasar dev or build right at the top in terminal?

[Propaganistas]

@rstoenescu Thanks for bearing with me. I'm using another build runner based on webpack with some sensible defaults preset (so not Quasar builder). I tracked it down to the defaults not including esModule: false in file-loader's options. Adding that fixed it.