It would be more useful to import the compiled template than the generated text

[vabruzzo]

It would be more useful to import the compiled template than the generated text

[bary12]

@thoughtbyte any thoughts about this? Take in mind that this is how webpack's ejs-loader works, and it seems to be a much better use for this plugin.

[wulisensen]

I very much agree with your suggestion.

I'm trying to use parcel from webpack.Now, i get a trouble about parcel-plugin-ejs: names is not defined.

<% if (names && names.length) { %> <% names.forEach(function(src,index){ %><video class="advideo" data-tag="<%= index %>"style="position:absolute;top:0;left:0;display:none;" poster="http://p1.ifengimg.com/a/2016/1021/loading0.jpg" src="<%= src %>" id="adPlayer" preload="auto"></video><% }) %> <% } %>

How to solve this problem now...

[vabruzzo]

yep, thanks for the suggestion. i will be updating this.

the reason i published this first is to sue as a base for a custom ejs plugin that will read variables directly from the template file, in the form of front-matter, but i will make this change here!

thanks!

[vabruzzo]

fixed in 0.2.0

[LucienLee]

How about work as pug in parcel?
put the data into ejs.config.js and compile with it
https://github.com/parcel-bundler/parcel/blob/75310e15f6fa3c8a0ce6593ada1bcca00240ea54/packages/core/parcel-bundler/src/assets/PugAsset.js#L36