-
Notifications
You must be signed in to change notification settings - Fork 32
loadPaths should be able to handle glob #40
Comments
@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 But i am sure there will be scenarios for other people when they would like to do something like |
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: |
@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: ['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. |
@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.The text was updated successfully, but these errors were encountered: