I've replicated the same issue using roots-records extension instead as the dynamic content generator against "api.bycarrot.com/staff"
;. Again, none of the dynamically generated files that are using the same layout and therefore the same "!= css()" and "!= js()" include the correct hashed filepaths. Also noticed the inclusion of either of these two extensions affects the hashed filenames generated for the css and js combined files. A regular jade file using the layout showed the following: <script src='/js/build.d41d8cd98f00b204e9800998ecf8427e.d41d8cd98f00b204e9800998ecf8427e.d6b53b53596e26481b4927c51b826a44.js'>. This file exists on disk so it looks like it passed through the hash function of js_pipeline several times, but only when either roots-contentful or roots-records it used.