Closed msacchetti closed 5 years ago
Isn't that expected? I believe it shouldn't process images during npm run watch
or npm run dev
. It should only process/compress during npm run prod
.
I was talking about when I'm developing the theme and I save an image to the resources/assets folder, I have to stop the watch process and rerun it because it does not get copied into the public folder (so subsequently the image path in my theme does not load, because it doesn't exist until I rerun watch).
edit: this is fixed now for some reason. closing
When i save an image to the resources/assets/images folder, webpack notices the addition of the file but does not process it and add it to the public directory. Is there a setting that will make this happen?