Orchard: Gulpfile.js doesn't support custom module and theme folders
Custom module and theme folders were introduced in 1.10 as a configurable item in web.config.
The gulpfile is still only looking in the original hard-coded locations for an assets.json file:
Code:
var assetManifestPaths = glob.sync("Orchard.Web/{Core,Modules,Themes}/*/Assets.json");
About this issue
- Original URL
- State: open
- Created 8 years ago
- Comments: 51 (51 by maintainers)
Actually, I’m thinking, since I’m reusing the gulp pipeline outside Orchard context. Maybe keeping things modular with it could be another approach. I mean, we actually could keep the actual gulpfile.js with generic functions and use an extension method to feed it’s list of paths to look at. From this point of view now, I think that parsing web.config file is only relevant for Orchard itself. Wich makes sense to keep the actual function to read the web.config file in it. But the other functions to read the list of custom paths should be directly in the gulpfile.js. But I have nothing against having it all in the gulpfile.js either … just another point of view 😄