Seth Kinast

I would like to get something like this in for Dust@3 in which I don't plan on supporting IE8. Shall we make this a getter?

I'll give it a look :) On Thu, Dec 7, 2017, 6:30 AM Ashwin Hegde wrote: > @kumarrishav have fixed the node 8 bug > here ... > can anyone...

What is `engines`? Are you using consolidate? If not, which rendering engine? What express version?

This looks pretty reasonable. I will be able to test an example tomorrow. Until then: Consolidate expects your files to end in .dust unless you pass it a different extension....

Yes, template paths in dust are absolute, not relative. I believe a couple people have worked on renderers that automatically transform relative paths. In dust, template names have to be...

What would you expect the compiler to output if you had two templates with the same name in different folders? If you have only one folder you can use the...

You could write a prebuild step into your build pipeline that merges all files into the same folder. Dust can't assume that all your files have unique names. On Mon,...

If you want the compiled file in each folder, you could just repeatedly run dustc on each folder instead of on the folder tree. Then dust wouldn't know about your...

If it's its own module that's effectively a monkeypatch. I think that it doesn't seem that useful because it's basically just sugar for one possible usecase, and it doesn't even...

@smfoote Dust won't support Promises like that for quite a long time. Although that means that `renderTo` probably needs a callback arg too, gross. @jimmyhchan html5shiv is the implementor's problem,...