Matthew Eernisse
Matthew Eernisse
@TimothyGu This is great. I'm back and forth with the owner of ejs.co, but the cost might be prohibitively high.
@puzrin, I assume you mean something other than the package.json? You want something that lives on the exported object?
I've done something like this before, making it part of the build/release process: https://github.com/mde/timezone-js/blob/master/src/date.js#L58 It makes total sense for client-side use. Could you open a GH Issue for this?
Looks like we'll be getting ejs.co for our doc site. I have just have to finalize the payment arrangements.
@puzrin, versioning-detection issue here: https://github.com/mde/ejs/issues/30
Site is on the way. First cut of it lives here for now: https://github.com/mde/ejs-site
New site is up at http://ejs.co -- not much there yet, basically just brochureware with a copy of what's in the README. But a step in the right direction.
It makes sense that this would happen — the `include`directive is a simple JS function that grabs the template off disk, evaluates it, and inserts the result at that `include`...
I've added a bunch of comments to PR #428. Interested to hear your thoughts.
This is indeed a critical upgrade -- however what do you think about the loss in clarity and debuggability that comes from removing the explicitly named function? Also, ES6 updates...