TJ
TJ
you'd have to pass it via options? seems a little weird, unless I'm misreading that, but it's not that simple, need caching etc, I haven't seen a good solid solution...
we should probably just wrap it so we can just use the ejs require within that function since it likely wont work with other require()s anyway
yeah, a lot wont though that's the issue. I had my express client working with identical templates, but I just used toString() on the function and sent that to the...
+1 to components, `component build --standalone` will do the other wrapping for us
let's do one at a time for now, and then components last
+1 for removal of filters, kinda weird, not sure why I added them
In this package I'd definitely like to just mirror their end-points 1:1, go-dropy can provide something more useful on top. I haven't started any work on it though I actually...
I've been using browserify instead now, not sure when I'll have time to update this though
oh boy haha, yikes :+1: