Closed aegyed91 closed 8 years ago
@tsm91 whats the use case of this?
@borodean if you have an asset-pipeline which is project-structure agnostic like this.
In my case it doesn't cause any problems because the images
gulp task will copy the image from anywhere to public/images
but only because i use gulp-flatten and because of the file watcher.
But i am sure there will be scenarios for other people when they would like to do something like src/**/*
or dist/**/*
.
I've just hit this myself as well, since we break things out into small modules we don't have a single root of assets anymore.
Being able to use: name/apps/*/img/
would be sweet :)
@tsm91 @dan-gamble here you go: introduced in 4.0.0.
Awesome <3
cool, thanks
@tsm91 @dan-gamble btw, the plugin now accepts a single string as a loadPaths
option, so instead of this:
loadPaths: ['assets/**/img']
You can also write this:
loadPaths: 'assets/**/img'
Thanks for the heads up :)
Hi @borodean, how to write the options about this url.
appName/src/assets/images/test.png
and css in appName/src/assets/css/main.css
resolve('test.png')
I try it a long time and throw error. Assets not found or unreadable
@anotherWill well, I assume something like this should work:
loadPaths: 'appName/src/assets/images'
Hi @borodean, I think the
loadPaths
option does not handle glob patterns. It would be an useful feature i think.