Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

assets not resolve with ~ symbol

See original GitHub issue

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;">

Issue Analytics

State:
Created 4 years ago
Reactions:4
Comments:14 (6 by maintainers)

Top GitHub Comments

2reactions

ggeorgiev92commented, Nov 26, 2019

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. unknown

1reaction

rstoenescucommented, Nov 27, 2019

Hi,

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

Top Results From Across the Web

0 - Stack Overflow

the code the Logo.png is opening even though it is showing error. Error: Unable to resolve module ../assets/Logo.png from.

Image component does not resolve images with filenames that ...

[Image] Retina Assets - Image component does not resolve images with filenames that include '@' symbol #14980. Resolution: Locked.

App Handling Assets | Quasar Framework

Asset Resolving Rules ... Relative URLs, e.g. ./assets/logo.png will be interpreted as a module dependency. They will be replaced with an auto-generated URL...

Xcode 10.1 did not fix the iOS 9 asset catalogs crash problem

I have removed all the assets (except app icons) from asset catalogs and re-imported them into the project "old school" style. It's not...

Handling Static Assets · GitBook

logo.png" is a relative asset path and will be resolved by Webpack as a module dependency. Because logo.png is not JavaScript, when treated...