YUI-Stockpile supports a custom template to build the combo url thru the loader that does not rely on the querystring (few reasons behind that [1]). E.g:
comboBase: "/combo~",
comboSep: "~"
I see few options here:
expose parseQuery routine so it can be hacked
provide some basic configurations to specify comboSep and comboBase, and use those to parse the url
This smells like middleware, to me. The second option (basic config) sounds cleaner to me, though I'm not sure comboBase ports directly from YUI config to combohandler's Express route convention.
YUI-Stockpile supports a custom template to build the combo url thru the loader that does not rely on the
querystring
(few reasons behind that [1]). E.g:I see few options here:
comboSep
andcomboBase
, and use those to parse the url[1] http://www.yuiblog.com/blog/2012/11/06/managing-your-javascript-modules-with-yui-3-stockpile-2/