-
Notifications
You must be signed in to change notification settings - Fork 3.4k
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
Fixing issues of image error when building dev #150
Conversation
Double confirmed this is compilable under Windows 7 grunt-cli v1.2.0 and npm 4.0.3 |
Hi @windhamwong, could you explain what the problem is that you're trying to fix? The webpack config is designed to support three different types of build:
Across all these builds, any images referenced in third party code (libraries) are inlined, so as to solve referencing issues. What are you hoping to achieve with this pull request? |
Thanks for the response and the explanation. |
That's not the behaviour I'm seeing (and it isn't how it should be working). I'd try updating your node and npm versions and reinstalling. I'll close this for now, but if you keep having problems, raise an issue with all the details of how to replicate it and we'll see what we can do to fix it. |
Using command |
This is what I get:
|
Menu translate
Fixing issues on packing images into build #webpack #base64 #loader
The problem now is that:
When you do
grunt dev
, all the images are double encoded with base64 and saved as files. By default, HTML do not load up data base64 images in this way, so I removed the loader part and images are now converted into data URI base64 inline in the HTML.I didn't try on build prod, but I assume it has the same issue. I can see that the Webpack part is still under development, this should temp fix for people who want to use the tool at the moment.