PR for issue #49

[KaiSchwarz-cnic]

a note concerning the use of new URL and url.parse:
https://stackoverflow.com/questions/46416439/unable-to-import-url-class-in-nodejs-typescript-app

Thus I am not sure if you're completely ok with this PR.

I also have not tried out if compiling a template by url works, I assume it does.

[KaiSchwarz-cnic]

Hey @cookpete

is there an update on this PR? : )
Don't worry, I don't want to pressure you - just want to ask if there's a timeline for this or if you do not plan to merge / to add that feature. Just some information so that we know how to proceed internally.

TIA!

[cookpete]

Hey Kai, I must admit I completely forgot about this.. sorry! I think the idea is good but I think we should separate the logic for fetching a template from a URL, so as to not affect the existing code too much (for a feature that won't be used very often) and also to stay working on all Node 6 versions (apparently the URL constructor was only added in 6.13.0).

[cookpete]

You can see my attempt to add support for this in b3a21db, published in 1.8.0. Let me know if it does the job.

[KaiSchwarz-cnic]

Thanks for pointing on that, but 1.7.2 is the most current version available on npm :)

[cookpete]

Should be up now 👍

[KaiSchwarz-cnic]

working ty! that was the reason why it did not work before. I exactly tried argument template with url in that way, but in version 1.7.2 :)