-
Notifications
You must be signed in to change notification settings - Fork 12k
WARNING in '...' (Emitted Value instead of an instance of Error) postcss-url: foo/select.component.css can't read file 'bar.svg', ignoring #10004
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Same Issue here... |
Solution is to add '/' to the beginning of the path: |
That worked! |
@Mozart-Alkhateeb your solution won't work if you build with base-ref (meaning using a virtual path). |
Solution is to add '/' to the beginning of the path: |
The issue should still be open. Like @ashraftm is stating, you can't always just prefix a '/' if you don't know from what sub folder your app will be hosted |
The modification of root relative paths in cases such as this is planned to be removed for 7.0. Also instead of making the path root relative with the |
@clydin prefixing with a ^ seems to have no other effect than changing the actual path to include the ^ symbol (%5E) |
Seems like the latest angular cli (v6) is not passing the base-href to the postcss, making postcss mess up the paths. I can't prefix my urls with / or with ../ since both will mess up the path. The path needs to be relative since i have a base-href for my solution. The angular CLI already reads the base-href and uses it for parsing assets, everywhere except passing it to postcss. Any paths inside .scss files will eventually work once the solution hits production, but in non prod builds, postcss will output errors/warnings since it does not know about the base-href |
I have the same error, it does not show me the images when compiling my application. :( when I use "../../ .." or "./ .." Any help? |
@Danielapariona virtual path won't work when you build your app, try '/[path]/img.png' |
Why is this closed? If your app is not hosted on root path Solution with adding There should be option to provide source for postcss only |
Any news? |
I encountered the same issue in stage env and finally found that's because I forgot to commit the image file. Resolved it by committing the image file to git repo. Hope this can help others. |
Same issue when importing font files from a node_module. Any input here? |
Any update ? |
I think a new issue should be opened |
Agreed, this should be reopened. |
Please reopen since no solution has been suggested. Thanks |
The original issue was against version 1.7.3 which is no longer supported. If you are encountering similar issues with a supported (or latest) version of the CLI, please open a new issue. Please ensure that all the requested information from the issue template is provided so that the team can properly assist you. |
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Versions
Repro steps
assets/images/*.*
Observed behavior
One of the referenced images:
Desired behavior
No warnings?
Mention any other details that might be useful (optional)
This seems to happen for any file where I reference a background image in css.
The text was updated successfully, but these errors were encountered: