{"_id":"phnq_ejs","_rev":"51-2caaa9df56f4df16725d5e893567fd21","name":"phnq_ejs","description":"Embedded JavaScript templating tool","dist-tags":{"latest":"1.0.9"},"versions":{"1.0.0":{"name":"phnq_ejs","description":"Embedded JavaScript templating tool","homepage":"https://github.com/pgostovic/phnq_ejs","keywords":["phnq","ejs","server","client","browser"],"author":{"name":"Patrick Gostovic","email":"pg@phnq.org"},"repository":{"type":"git","url":"git://github.com/pgostovic/phnq_ejs.git"},"main":"phnq_ejs.js","version":"1.0.0","dependencies":{"phnq_log":"1.0.1"},"_npmUser":{"name":"pgostovic","email":"pg@phnq.org"},"_id":"phnq_ejs@1.0.0","devDependencies":{},"optionalDependencies":{},"engines":{"node":"*"},"_engineSupported":true,"_npmVersion":"1.1.1","_nodeVersion":"v0.6.11","_defaultsLoaded":true,"dist":{"shasum":"6033f879941fc3a1dfd44019345346c37b3103a7","tarball":"https://registry.npmjs.org/phnq_ejs/-/phnq_ejs-1.0.0.tgz","integrity":"sha512-XM+NLfcQ/u4msMCHndMffVr3urmMBksZU8GkFlDSdUsuZsVsdIBvYI4yFJ/7WOFg2HZ+P6D7GC3QRBGKAhz6MA==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIQCcwdD2qgOzDL+J6OsOTTKdQPURboSI8huttdPK5d1yWAIgJePxh5uuAQe5a3D1hkQbVr1p/fYEvexmNMzcs9Pa5GU="}]},"maintainers":[{"name":"pgostovic","email":"pg@phnq.org"}],"directories":{}},"1.0.1":{"name":"phnq_ejs","description":"Embedded JavaScript templating tool","homepage":"https://github.com/pgostovic/phnq_ejs","keywords":["phnq","ejs","server","client","browser"],"author":{"name":"Patrick Gostovic","email":"pg@phnq.org"},"repository":{"type":"git","url":"git://github.com/pgostovic/phnq_ejs.git"},"main":"phnq_ejs.js","version":"1.0.1","dependencies":{"phnq_log":"1.0.x","phnq_core":"1.0.x"},"readme":"phnq_ejs - EJS Templates\n========================\nThe phnq_ejs module is simple templating utility that uses embedded JavaScript. It's inspired by several familiar embedded language templating systems such as ERB, JSP, ASP, etc. EJS uses the same notation as the aforementioned systems for embedding dynamic code into templates.  For example:\n\n\t<%= foo %>\n\nThis will cause the result of the statement \"foo\" to be rendered.  So, if the value of \"foo\" were \"bar\", then the following...\n\n\t<h1><%= foo %></h1>\n\n...would evaluate to:\n\n\t<h1>bar</h1>\n\nBlocks of JavaScript are embedded with the <% %> notation.  For example:\n\n\t<% for(var i=0; i<5; i++) { %>\n\t\t<div>Number <%= i %></div>\n\t<% } %>\n\nThe above code would render as follows:\n\n\t<div>Number 0</div>\n\t<div>Number 1</div>\n\t<div>Number 2</div>\n\t<div>Number 3</div>\n\t<div>Number 4</div>\n\nVery basic. Very simple.\n\n\nBasic Usage\n-----------\n\nImport the phnq_ejs module:\n\n\tvar phnq_ejs = require(\"phnq_ejs\");\n\nOr on the client just include the file.\n\nCompile your template as a string:\n\n\tvar compiled = phnq_ejs.compile(someString);\n\nThe compiled result is a string that can be eval'd to a function. For example:\n\n\tvar fn = eval(compiled);\n\nThe result of executing the function will be the template rendered into a string.\n\nExample\n-------\n\nSuppose the variable \"tmplt\" held the following string:\n\n\t<ul>\n\t\t<% for(var i=0; i<3; i++) { %>\n\t\t\t<li><%= i %></li>\n\t\t<% } %>\n\t</ul>\n\nCompile that template string as follows:\n\n\tvar compiled = phnq_ejs.compile(tmplt);\n\nTurn the compiled code into a function like this:\n\n\tvar fn = eval(compiled);\n\nRender the template by calling the function:\n\n\tvar output = fn();\n\nIn this examle, \"output\" would be the following:\n\n\t<ul>\n\t\t<li>0</li>\n\t\t<li>1</li>\n\t\t<li>2</li>\n\t</ul>\n\nParameters\n----------\n\nSuppose you have the following template in the variable \"tmplt\":\n\n\t<div>\n\t\tName: <%= user.name %><br/>\n\t\tEmail: <%= user.email %><br/>\n\t</div>\n\nWhere does the \"user\" object come from? It is not declared anywhere in the template. The answer is that information can be passed into the function that is eval's from the compiled code. For example:\n\nCompile and eval to a function:\n\n\tvar compiled = phnq_ejs.compile(tmplt);\n\tvar fn = eval(compiled);\n\nThe resulting function can optionally take a single argument, an object that represents all of the \"local\" variables that are referenced from the template.  For example:\n\n\tvar user = { name: \"Bubba Gump\", email: \"bubba@gump.com\" };\n\n\tvar output = fn({user: user});\n\nThe resulting output in this case would be:\n\n\t<div>\n\t\tName: Bubba Gump<br/>\n\t\tEmail: bubba@gump.com<br/>\n\t</div>\n\n","_id":"phnq_ejs@1.0.1","dist":{"shasum":"ff924e7d2a5ae464aec3ec427f455e21c25f4bc0","tarball":"https://registry.npmjs.org/phnq_ejs/-/phnq_ejs-1.0.1.tgz","integrity":"sha512-S1Z+w2DBrq0jPl0A1qiOp+CEDy6SHN57ILhTbEqP2D0WK/wyvV/Up1i14wwfQ0ZDw+24+w+9oO8rHedf82vxCg==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEQCIChFPutcFWYLvCpg+JoDfxZ7oSWoH4XAMBSLCkmRG1djAiBfMo5GvGmpWHZpPD4u7jEe+Sw2G7WaPuNa19fj1mdFrw=="}]},"_npmVersion":"1.1.61","_npmUser":{"name":"pgostovic","email":"pg@phnq.org"},"maintainers":[{"name":"pgostovic","email":"pg@phnq.org"}],"directories":{}},"1.0.2":{"name":"phnq_ejs","description":"Embedded JavaScript templating tool","homepage":"https://github.com/pgostovic/phnq_ejs","keywords":["phnq","ejs","server","client","browser"],"author":{"name":"Patrick Gostovic","email":"pg@phnq.org"},"repository":{"type":"git","url":"git://github.com/pgostovic/phnq_ejs.git"},"main":"phnq_ejs.js","version":"1.0.2","dependencies":{"phnq_log":"1.0.x","phnq_core":"1.0.x"},"readme":"phnq_ejs - EJS Templates\n========================\nThe phnq_ejs module is simple templating utility that uses embedded JavaScript. It's inspired by several familiar embedded language templating systems such as ERB, JSP, ASP, etc. EJS uses the same notation as the aforementioned systems for embedding dynamic code into templates.  For example:\n\n\t<%= foo %>\n\nThis will cause the result of the statement \"foo\" to be rendered.  So, if the value of \"foo\" were \"bar\", then the following...\n\n\t<h1><%= foo %></h1>\n\n...would evaluate to:\n\n\t<h1>bar</h1>\n\nBlocks of JavaScript are embedded with the <% %> notation.  For example:\n\n\t<% for(var i=0; i<5; i++) { %>\n\t\t<div>Number <%= i %></div>\n\t<% } %>\n\nThe above code would render as follows:\n\n\t<div>Number 0</div>\n\t<div>Number 1</div>\n\t<div>Number 2</div>\n\t<div>Number 3</div>\n\t<div>Number 4</div>\n\nVery basic. Very simple.\n\n\nBasic Usage\n-----------\n\nImport the phnq_ejs module:\n\n\tvar phnq_ejs = require(\"phnq_ejs\");\n\nOr on the client just include the file.\n\nCompile your template as a string:\n\n\tvar compiled = phnq_ejs.compile(someString);\n\nThe compiled result is a string that can be eval'd to a function. For example:\n\n\tvar fn = eval(compiled);\n\nThe result of executing the function will be the template rendered into a string.\n\nExample\n-------\n\nSuppose the variable \"tmplt\" held the following string:\n\n\t<ul>\n\t\t<% for(var i=0; i<3; i++) { %>\n\t\t\t<li><%= i %></li>\n\t\t<% } %>\n\t</ul>\n\nCompile that template string as follows:\n\n\tvar compiled = phnq_ejs.compile(tmplt);\n\nTurn the compiled code into a function like this:\n\n\tvar fn = eval(compiled);\n\nRender the template by calling the function:\n\n\tvar output = fn();\n\nIn this examle, \"output\" would be the following:\n\n\t<ul>\n\t\t<li>0</li>\n\t\t<li>1</li>\n\t\t<li>2</li>\n\t</ul>\n\nParameters\n----------\n\nSuppose you have the following template in the variable \"tmplt\":\n\n\t<div>\n\t\tName: <%= user.name %><br/>\n\t\tEmail: <%= user.email %><br/>\n\t</div>\n\nWhere does the \"user\" object come from? It is not declared anywhere in the template. The answer is that information can be passed into the function that is eval's from the compiled code. For example:\n\nCompile and eval to a function:\n\n\tvar compiled = phnq_ejs.compile(tmplt);\n\tvar fn = eval(compiled);\n\nThe resulting function can optionally take a single argument, an object that represents all of the \"local\" variables that are referenced from the template.  For example:\n\n\tvar user = { name: \"Bubba Gump\", email: \"bubba@gump.com\" };\n\n\tvar output = fn({user: user});\n\nThe resulting output in this case would be:\n\n\t<div>\n\t\tName: Bubba Gump<br/>\n\t\tEmail: bubba@gump.com<br/>\n\t</div>\n\n","_id":"phnq_ejs@1.0.2","dist":{"shasum":"dd3033b409aaa803a7c8cb1b9d7565e03948eeea","tarball":"https://registry.npmjs.org/phnq_ejs/-/phnq_ejs-1.0.2.tgz","integrity":"sha512-mcuPmZltFpngcTLUexhrIGeAO2tyfc32ThXbovtaxKSDGQhwgTb296ILjaPJVt0eSNMBXpkWsGoAEY0T3TF4xg==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEQCID6jbIT1IUmiFHf3mCbVsJsvxQD0rFz0TVFDXf38UyxAAiB2UmSFPoGxxqVfs2ayR+CLppAG+T3NxhtGAryQ9LBEKA=="}]},"_npmVersion":"1.1.61","_npmUser":{"name":"pgostovic","email":"pg@phnq.org"},"maintainers":[{"name":"pgostovic","email":"pg@phnq.org"}],"directories":{}},"1.0.3":{"name":"phnq_ejs","description":"Embedded JavaScript templating tool","homepage":"https://github.com/pgostovic/phnq_ejs","keywords":["phnq","ejs","server","client","browser"],"author":{"name":"Patrick Gostovic","email":"pg@phnq.org"},"repository":{"type":"git","url":"git://github.com/pgostovic/phnq_ejs.git"},"main":"phnq_ejs.js","version":"1.0.3","dependencies":{"phnq_log":"1.0.x","phnq_core":"1.0.x"},"readme":"phnq_ejs - EJS Templates\n========================\nThe phnq_ejs module is simple templating utility that uses embedded JavaScript. It's inspired by several familiar embedded language templating systems such as ERB, JSP, ASP, etc. EJS uses the same notation as the aforementioned systems for embedding dynamic code into templates.  For example:\n\n\t<%= foo %>\n\nThis will cause the result of the statement \"foo\" to be rendered.  So, if the value of \"foo\" were \"bar\", then the following...\n\n\t<h1><%= foo %></h1>\n\n...would evaluate to:\n\n\t<h1>bar</h1>\n\nBlocks of JavaScript are embedded with the <% %> notation.  For example:\n\n\t<% for(var i=0; i<5; i++) { %>\n\t\t<div>Number <%= i %></div>\n\t<% } %>\n\nThe above code would render as follows:\n\n\t<div>Number 0</div>\n\t<div>Number 1</div>\n\t<div>Number 2</div>\n\t<div>Number 3</div>\n\t<div>Number 4</div>\n\nVery basic. Very simple.\n\n\nBasic Usage\n-----------\n\nImport the phnq_ejs module:\n\n\tvar phnq_ejs = require(\"phnq_ejs\");\n\nOr on the client just include the file.\n\nCompile your template as a string:\n\n\tvar compiled = phnq_ejs.compile(someString);\n\nThe compiled result is a string that can be eval'd to a function. For example:\n\n\tvar fn = eval(compiled);\n\nThe result of executing the function will be the template rendered into a string.\n\nExample\n-------\n\nSuppose the variable \"tmplt\" held the following string:\n\n\t<ul>\n\t\t<% for(var i=0; i<3; i++) { %>\n\t\t\t<li><%= i %></li>\n\t\t<% } %>\n\t</ul>\n\nCompile that template string as follows:\n\n\tvar compiled = phnq_ejs.compile(tmplt);\n\nTurn the compiled code into a function like this:\n\n\tvar fn = eval(compiled);\n\nRender the template by calling the function:\n\n\tvar output = fn();\n\nIn this examle, \"output\" would be the following:\n\n\t<ul>\n\t\t<li>0</li>\n\t\t<li>1</li>\n\t\t<li>2</li>\n\t</ul>\n\nParameters\n----------\n\nSuppose you have the following template in the variable \"tmplt\":\n\n\t<div>\n\t\tName: <%= user.name %><br/>\n\t\tEmail: <%= user.email %><br/>\n\t</div>\n\nWhere does the \"user\" object come from? It is not declared anywhere in the template. The answer is that information can be passed into the function that is eval's from the compiled code. For example:\n\nCompile and eval to a function:\n\n\tvar compiled = phnq_ejs.compile(tmplt);\n\tvar fn = eval(compiled);\n\nThe resulting function can optionally take a single argument, an object that represents all of the \"local\" variables that are referenced from the template.  For example:\n\n\tvar user = { name: \"Bubba Gump\", email: \"bubba@gump.com\" };\n\n\tvar output = fn({user: user});\n\nThe resulting output in this case would be:\n\n\t<div>\n\t\tName: Bubba Gump<br/>\n\t\tEmail: bubba@gump.com<br/>\n\t</div>\n\n","_id":"phnq_ejs@1.0.3","dist":{"shasum":"ab56470dfe677ac8bc25e615838ac11c3f1ef302","tarball":"https://registry.npmjs.org/phnq_ejs/-/phnq_ejs-1.0.3.tgz","integrity":"sha512-SE1v5lZ7JtqYd6ZMneSjgBiK4kyhp7oyqUTsHM2ywGqiocaGxbpTrZcNADxybleoEsDFaBrzu17EtMtITw8wSw==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQCJytdAW7WYRcDforL1q1ZfkK1KIXDynB8Qcz46nzs+pAIhAI8N1kmptKbJP9av8zsgGzJL66sGhFXVf0+Q428zXE/b"}]},"_npmVersion":"1.1.61","_npmUser":{"name":"pgostovic","email":"pg@phnq.org"},"maintainers":[{"name":"pgostovic","email":"pg@phnq.org"}],"directories":{}},"1.0.4":{"name":"phnq_ejs","description":"Embedded JavaScript templating tool","homepage":"https://github.com/pgostovic/phnq_ejs","keywords":["phnq","ejs","server","client","browser"],"author":{"name":"Patrick Gostovic","email":"pg@phnq.org"},"repository":{"type":"git","url":"git://github.com/pgostovic/phnq_ejs.git"},"main":"phnq_ejs.js","version":"1.0.4","dependencies":{"phnq_log":"1.0.x","phnq_core":"1.0.x"},"readme":"phnq_ejs - EJS Templates\n========================\nThe phnq_ejs module is simple templating utility that uses embedded JavaScript. It's inspired by several familiar embedded language templating systems such as ERB, JSP, ASP, etc. EJS uses the same notation as the aforementioned systems for embedding dynamic code into templates.  For example:\n\n\t<%= foo %>\n\nThis will cause the result of the statement \"foo\" to be rendered.  So, if the value of \"foo\" were \"bar\", then the following...\n\n\t<h1><%= foo %></h1>\n\n...would evaluate to:\n\n\t<h1>bar</h1>\n\nBlocks of JavaScript are embedded with the <% %> notation.  For example:\n\n\t<% for(var i=0; i<5; i++) { %>\n\t\t<div>Number <%= i %></div>\n\t<% } %>\n\nThe above code would render as follows:\n\n\t<div>Number 0</div>\n\t<div>Number 1</div>\n\t<div>Number 2</div>\n\t<div>Number 3</div>\n\t<div>Number 4</div>\n\nVery basic. Very simple.\n\n\nBasic Usage\n-----------\n\nImport the phnq_ejs module:\n\n\tvar phnq_ejs = require(\"phnq_ejs\");\n\nOr on the client just include the file.\n\nCompile your template as a string:\n\n\tvar compiled = phnq_ejs.compile(someString);\n\nThe compiled result is a string that can be eval'd to a function. For example:\n\n\tvar fn = eval(compiled);\n\nThe result of executing the function will be the template rendered into a string.\n\nExample\n-------\n\nSuppose the variable \"tmplt\" held the following string:\n\n\t<ul>\n\t\t<% for(var i=0; i<3; i++) { %>\n\t\t\t<li><%= i %></li>\n\t\t<% } %>\n\t</ul>\n\nCompile that template string as follows:\n\n\tvar compiled = phnq_ejs.compile(tmplt);\n\nTurn the compiled code into a function like this:\n\n\tvar fn = eval(compiled);\n\nRender the template by calling the function:\n\n\tvar output = fn();\n\nIn this examle, \"output\" would be the following:\n\n\t<ul>\n\t\t<li>0</li>\n\t\t<li>1</li>\n\t\t<li>2</li>\n\t</ul>\n\nParameters\n----------\n\nSuppose you have the following template in the variable \"tmplt\":\n\n\t<div>\n\t\tName: <%= user.name %><br/>\n\t\tEmail: <%= user.email %><br/>\n\t</div>\n\nWhere does the \"user\" object come from? It is not declared anywhere in the template. The answer is that information can be passed into the function that is eval's from the compiled code. For example:\n\nCompile and eval to a function:\n\n\tvar compiled = phnq_ejs.compile(tmplt);\n\tvar fn = eval(compiled);\n\nThe resulting function can optionally take a single argument, an object that represents all of the \"local\" variables that are referenced from the template.  For example:\n\n\tvar user = { name: \"Bubba Gump\", email: \"bubba@gump.com\" };\n\n\tvar output = fn({user: user});\n\nThe resulting output in this case would be:\n\n\t<div>\n\t\tName: Bubba Gump<br/>\n\t\tEmail: bubba@gump.com<br/>\n\t</div>\n\n","_id":"phnq_ejs@1.0.4","dist":{"shasum":"943755c870d7ee1251ba62f100391d2b2c14a490","tarball":"https://registry.npmjs.org/phnq_ejs/-/phnq_ejs-1.0.4.tgz","integrity":"sha512-+64CHklWB9OwMlJtH865r+53k5e+hxg4jruty7wNEDtZt0ewg05ziGRIJX9Bkv24TtN2ivxD/cQuZ5y62LAfLw==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIGwj0KhsKw9EomB66lVYOOrt3jVuXcKXBVqVks5NM1IPAiEA+LH/vS5ZqSQMdKygyPhVjVylVj4z6ueoywjjiYh/Atg="}]},"_npmVersion":"1.1.61","_npmUser":{"name":"pgostovic","email":"pg@phnq.org"},"maintainers":[{"name":"pgostovic","email":"pg@phnq.org"}],"directories":{}},"1.0.5":{"name":"phnq_ejs","description":"Embedded JavaScript templating tool","homepage":"https://github.com/pgostovic/phnq_ejs","keywords":["phnq","ejs","server","client","browser"],"author":{"name":"Patrick Gostovic","email":"pg@phnq.org"},"repository":{"type":"git","url":"git://github.com/pgostovic/phnq_ejs.git"},"main":"phnq_ejs.js","version":"1.0.5","dependencies":{"phnq_log":"1.0.x","phnq_core":"1.0.x","mocha":"1.6.0"},"scripts":{"test":"mocha"},"engines":{"node":"0.8.x"},"readme":"phnq_ejs - EJS Templates\n========================\nThe phnq_ejs module is simple templating utility that uses embedded JavaScript. It's inspired by several familiar embedded language templating systems such as ERB, JSP, ASP, etc. EJS uses the same notation as the aforementioned systems for embedding dynamic code into templates.  For example:\n\n\t<%= foo %>\n\nThis will cause the result of the statement \"foo\" to be rendered.  So, if the value of \"foo\" were \"bar\", then the following...\n\n\t<h1><%= foo %></h1>\n\n...would evaluate to:\n\n\t<h1>bar</h1>\n\nBlocks of JavaScript are embedded with the <% %> notation.  For example:\n\n\t<% for(var i=0; i<5; i++) { %>\n\t\t<div>Number <%= i %></div>\n\t<% } %>\n\nThe above code would render as follows:\n\n\t<div>Number 0</div>\n\t<div>Number 1</div>\n\t<div>Number 2</div>\n\t<div>Number 3</div>\n\t<div>Number 4</div>\n\nVery basic. Very simple.\n\n\nBasic Usage\n-----------\n\nImport the phnq_ejs module:\n\n\tvar phnq_ejs = require(\"phnq_ejs\");\n\nOr on the client just include the file.\n\nCompile your template as a string:\n\n\tvar compiled = phnq_ejs.compile(someString);\n\nThe compiled result is a string that can be eval'd to a function. For example:\n\n\tvar fn = eval(compiled);\n\nThe result of executing the function will be the template rendered into a string.\n\nExample\n-------\n\nSuppose the variable \"tmplt\" held the following string:\n\n\t<ul>\n\t\t<% for(var i=0; i<3; i++) { %>\n\t\t\t<li><%= i %></li>\n\t\t<% } %>\n\t</ul>\n\nCompile that template string as follows:\n\n\tvar compiled = phnq_ejs.compile(tmplt);\n\nTurn the compiled code into a function like this:\n\n\tvar fn = eval(compiled);\n\nRender the template by calling the function:\n\n\tvar output = fn();\n\nIn this examle, \"output\" would be the following:\n\n\t<ul>\n\t\t<li>0</li>\n\t\t<li>1</li>\n\t\t<li>2</li>\n\t</ul>\n\nParameters\n----------\n\nSuppose you have the following template in the variable \"tmplt\":\n\n\t<div>\n\t\tName: <%= user.name %><br/>\n\t\tEmail: <%= user.email %><br/>\n\t</div>\n\nWhere does the \"user\" object come from? It is not declared anywhere in the template. The answer is that information can be passed into the function that is eval's from the compiled code. For example:\n\nCompile and eval to a function:\n\n\tvar compiled = phnq_ejs.compile(tmplt);\n\tvar fn = eval(compiled);\n\nThe resulting function can optionally take a single argument, an object that represents all of the \"local\" variables that are referenced from the template.  For example:\n\n\tvar user = { name: \"Bubba Gump\", email: \"bubba@gump.com\" };\n\n\tvar output = fn({user: user});\n\nThe resulting output in this case would be:\n\n\t<div>\n\t\tName: Bubba Gump<br/>\n\t\tEmail: bubba@gump.com<br/>\n\t</div>\n\n","_id":"phnq_ejs@1.0.5","dist":{"shasum":"0c6f1b40de857c7682eaa9aec5e522541245a44b","tarball":"https://registry.npmjs.org/phnq_ejs/-/phnq_ejs-1.0.5.tgz","integrity":"sha512-V+a54GS1yBgilblW9JEvl8js3Yr8qXL01E7+pnstoPqQcXA10sagspJRP1wx28GMxNyw0UjdL+eXYxwiP2gX6Q==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCICsLpWWgF/CjC3Rzdvc8zhVhqBTnliH+hTx9TDjNNwamAiEA2O8ovAFJMeOgpRn9FPMOVtUTg5clCY5BE2xJFaJ+l1M="}]},"_npmVersion":"1.1.61","_npmUser":{"name":"pgostovic","email":"pg@phnq.org"},"maintainers":[{"name":"pgostovic","email":"pg@phnq.org"}],"directories":{}},"1.0.6":{"name":"phnq_ejs","description":"Embedded JavaScript templating tool","homepage":"https://github.com/pgostovic/phnq_ejs","keywords":["phnq","ejs","server","client","browser"],"author":{"name":"Patrick Gostovic","email":"pg@phnq.org"},"repository":{"type":"git","url":"git://github.com/pgostovic/phnq_ejs.git"},"main":"phnq_ejs.js","version":"1.0.6","dependencies":{"phnq_log":"1.0.x","phnq_core":"1.0.x","mocha":"1.6.0"},"scripts":{"test":"mocha"},"engines":{"node":"0.8.x"},"readme":"phnq_ejs - EJS Templates\n========================\nThe phnq_ejs module is simple templating utility that uses embedded JavaScript. It's inspired by several familiar embedded language templating systems such as ERB, JSP, ASP, etc. EJS uses the same notation as the aforementioned systems for embedding dynamic code into templates.  For example:\n\n\t<%= foo %>\n\nThis will cause the result of the statement \"foo\" to be rendered.  So, if the value of \"foo\" were \"bar\", then the following...\n\n\t<h1><%= foo %></h1>\n\n...would evaluate to:\n\n\t<h1>bar</h1>\n\nBlocks of JavaScript are embedded with the <% %> notation.  For example:\n\n\t<% for(var i=0; i<5; i++) { %>\n\t\t<div>Number <%= i %></div>\n\t<% } %>\n\nThe above code would render as follows:\n\n\t<div>Number 0</div>\n\t<div>Number 1</div>\n\t<div>Number 2</div>\n\t<div>Number 3</div>\n\t<div>Number 4</div>\n\nVery basic. Very simple.\n\n\nBasic Usage\n-----------\n\nImport the phnq_ejs module:\n\n\tvar phnq_ejs = require(\"phnq_ejs\");\n\nOr on the client just include the file.\n\nCompile your template as a string:\n\n\tvar compiled = phnq_ejs.compile(someString);\n\nThe compiled result is a string that can be eval'd to a function. For example:\n\n\tvar fn = eval(compiled);\n\nThe result of executing the function will be the template rendered into a string.\n\nExample\n-------\n\nSuppose the variable \"tmplt\" held the following string:\n\n\t<ul>\n\t\t<% for(var i=0; i<3; i++) { %>\n\t\t\t<li><%= i %></li>\n\t\t<% } %>\n\t</ul>\n\nCompile that template string as follows:\n\n\tvar compiled = phnq_ejs.compile(tmplt);\n\nTurn the compiled code into a function like this:\n\n\tvar fn = eval(compiled);\n\nRender the template by calling the function:\n\n\tvar output = fn();\n\nIn this examle, \"output\" would be the following:\n\n\t<ul>\n\t\t<li>0</li>\n\t\t<li>1</li>\n\t\t<li>2</li>\n\t</ul>\n\nParameters\n----------\n\nSuppose you have the following template in the variable \"tmplt\":\n\n\t<div>\n\t\tName: <%= user.name %><br/>\n\t\tEmail: <%= user.email %><br/>\n\t</div>\n\nWhere does the \"user\" object come from? It is not declared anywhere in the template. The answer is that information can be passed into the function that is eval's from the compiled code. For example:\n\nCompile and eval to a function:\n\n\tvar compiled = phnq_ejs.compile(tmplt);\n\tvar fn = eval(compiled);\n\nThe resulting function can optionally take a single argument, an object that represents all of the \"local\" variables that are referenced from the template.  For example:\n\n\tvar user = { name: \"Bubba Gump\", email: \"bubba@gump.com\" };\n\n\tvar output = fn({user: user});\n\nThe resulting output in this case would be:\n\n\t<div>\n\t\tName: Bubba Gump<br/>\n\t\tEmail: bubba@gump.com<br/>\n\t</div>\n\n","_id":"phnq_ejs@1.0.6","dist":{"shasum":"0f56dfa75ea8042e40582f7bc7e4ddb2a5fdc1fa","tarball":"https://registry.npmjs.org/phnq_ejs/-/phnq_ejs-1.0.6.tgz","integrity":"sha512-dAsBnTy0mIcC8ZjZnXYQfC6DvYcjKWCyBOzMoZ/x66GodRY3lQ3XKvnz92FWWgYrre0yCG/CeVo9CyGU/wyZcg==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQCHOyzvZrmTqSj8arVyS299B0HAgXzHSPljr6pu9VKBwAIhAJJ3urxdst8rfIffzs2PhrjYqo0uS1K3++w+bkarDSwv"}]},"_npmVersion":"1.1.61","_npmUser":{"name":"pgostovic","email":"pg@phnq.org"},"maintainers":[{"name":"pgostovic","email":"pg@phnq.org"}],"directories":{}},"1.0.7":{"name":"phnq_ejs","description":"Embedded JavaScript templating tool","homepage":"https://github.com/pgostovic/phnq_ejs","keywords":["phnq","ejs","server","client","browser"],"author":{"name":"Patrick Gostovic","email":"pg@phnq.org"},"repository":{"type":"git","url":"git://github.com/pgostovic/phnq_ejs.git"},"main":"phnq_ejs.js","version":"1.0.7","dependencies":{"phnq_log":"1.0.x","phnq_core":"1.0.x","mocha":"1.6.0"},"scripts":{"test":"mocha"},"engines":{"node":"0.8.x"},"readme":"phnq_ejs - EJS Templates\n========================\nThe phnq_ejs module is simple templating utility that uses embedded JavaScript. It's inspired by several familiar embedded language templating systems such as ERB, JSP, ASP, etc. EJS uses the same notation as the aforementioned systems for embedding dynamic code into templates.  For example:\n\n\t<%= foo %>\n\nThis will cause the result of the statement \"foo\" to be rendered.  So, if the value of \"foo\" were \"bar\", then the following...\n\n\t<h1><%= foo %></h1>\n\n...would evaluate to:\n\n\t<h1>bar</h1>\n\nBlocks of JavaScript are embedded with the <% %> notation.  For example:\n\n\t<% for(var i=0; i<5; i++) { %>\n\t\t<div>Number <%= i %></div>\n\t<% } %>\n\nThe above code would render as follows:\n\n\t<div>Number 0</div>\n\t<div>Number 1</div>\n\t<div>Number 2</div>\n\t<div>Number 3</div>\n\t<div>Number 4</div>\n\nVery basic. Very simple.\n\nExpressions\n-----------\nAn alternate syntax, called expressions, is also available. For example:\n\n\t${foo}\n\nThis is equivalent to:\n\n\t<%= foo %>\n\nAnother example:\n\n\t{if true}\n\t\t<p>truth</p>\n\t{/if}\n\nThis is equivalent to:\n\n\t<% if(true) { %>\n\t\t<p>truth</p>\n\t<% } %>\n\nNotice the dollar sign in the ${foo} example and the lack of dollar sign in the {if} example. The syntax with the dollar sign just renders a JavaScript value.  The syntax without the dollar sign must adgere to xml-like syntax. That is, these \"tags\" must be well-formed; each open tag must have a corresponding closing tag, or they must be empty. These \"structured\" expressions are treated like functions, unless their \"tag\" name is one of if, else, while or for, in which case they are treated like control structures. For example:\n\n\t{for var i=0; i<5; i++}\n\t\t<div>Number ${i}</div>\n\t{/for}\n\nThis is a slightly more elegant way to achieve one of the previous examples.\n\n\nBasic Usage\n-----------\n\nImport the phnq_ejs module:\n\n\tvar phnq_ejs = require(\"phnq_ejs\");\n\nOr on the client just include the file.\n\nCompile your template as a string:\n\n\tvar compiled = phnq_ejs.compile(someString);\n\nThe compiled result is a string that can be eval'd to a function. For example:\n\n\tvar fn = eval(compiled);\n\nThe result of executing the function will be the template rendered into a string.\n\nExample\n-------\n\nSuppose the variable \"tmplt\" held the following string:\n\n\t<ul>\n\t\t<% for(var i=0; i<3; i++) { %>\n\t\t\t<li><%= i %></li>\n\t\t<% } %>\n\t</ul>\n\nCompile that template string as follows:\n\n\tvar compiled = phnq_ejs.compile(tmplt);\n\nTurn the compiled code into a function like this:\n\n\tvar fn = eval(compiled);\n\nRender the template by calling the function:\n\n\tvar output = fn();\n\nIn this examle, \"output\" would be the following:\n\n\t<ul>\n\t\t<li>0</li>\n\t\t<li>1</li>\n\t\t<li>2</li>\n\t</ul>\n\nParameters\n----------\n\nSuppose you have the following template in the variable \"tmplt\":\n\n\t<div>\n\t\tName: <%= user.name %><br/>\n\t\tEmail: <%= user.email %><br/>\n\t</div>\n\nWhere does the \"user\" object come from? It is not declared anywhere in the template. The answer is that information can be passed into the function that is eval's from the compiled code. For example:\n\nCompile and eval to a function:\n\n\tvar compiled = phnq_ejs.compile(tmplt);\n\tvar fn = eval(compiled);\n\nThe resulting function can optionally take a single argument, an object that represents all of the \"local\" variables that are referenced from the template.  For example:\n\n\tvar user = { name: \"Bubba Gump\", email: \"bubba@gump.com\" };\n\n\tvar output = fn({user: user});\n\nThe resulting output in this case would be:\n\n\t<div>\n\t\tName: Bubba Gump<br/>\n\t\tEmail: bubba@gump.com<br/>\n\t</div>\n\n","_id":"phnq_ejs@1.0.7","dist":{"shasum":"79b25fd2b76068c8ee3e44e637e3f5bf02aec664","tarball":"https://registry.npmjs.org/phnq_ejs/-/phnq_ejs-1.0.7.tgz","integrity":"sha512-2DMn6hiL3rkeqLEi3s3mUBY+/hQjeOOstis1Wj2sQxptH0tQxBYQ6akUNadt0aCkUC/1sqeqeSJPodwdwYL7Ww==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIQD9jodyQMePxIqA4pc8xvGxKxA160nkuTGVQ+dLGp29gAIgNDbmW4F7zt6gw7F2NTfnNN3ok8Mf5z0D8U3hroRTKWg="}]},"_npmVersion":"1.1.61","_npmUser":{"name":"pgostovic","email":"pg@phnq.org"},"maintainers":[{"name":"pgostovic","email":"pg@phnq.org"}]},"1.0.8":{"name":"phnq_ejs","description":"Embedded JavaScript templating tool","homepage":"https://github.com/pgostovic/phnq_ejs","keywords":["phnq","ejs","server","client","browser"],"author":{"name":"Patrick Gostovic","email":"pg@phnq.org"},"repository":{"type":"git","url":"git://github.com/pgostovic/phnq_ejs.git"},"main":"phnq_ejs.js","version":"1.0.8","dependencies":{"phnq_log":"1.0.x","phnq_core":"1.0.x","mocha":"1.6.0"},"scripts":{"test":"mocha -R spec"},"engines":{"node":"0.8.x"},"readme":"phnq_ejs - EJS Templates\n========================\nThe phnq_ejs module is simple templating utility that uses embedded JavaScript. It's inspired by several familiar embedded language templating systems such as ERB, JSP, ASP, etc. EJS uses the same notation as the aforementioned systems for embedding dynamic code into templates.  For example:\n\n\t<%= foo %>\n\nThis will cause the result of the statement \"foo\" to be rendered.  So, if the value of \"foo\" were \"bar\", then the following...\n\n\t<h1><%= foo %></h1>\n\n...would evaluate to:\n\n\t<h1>bar</h1>\n\nBlocks of JavaScript are embedded with the <% %> notation.  For example:\n\n\t<% for(var i=0; i<5; i++) { %>\n\t\t<div>Number <%= i %></div>\n\t<% } %>\n\nThe above code would render as follows:\n\n\t<div>Number 0</div>\n\t<div>Number 1</div>\n\t<div>Number 2</div>\n\t<div>Number 3</div>\n\t<div>Number 4</div>\n\nVery basic. Very simple.\n\nExpressions\n-----------\nAn alternate syntax, called expressions, is also available. For example:\n\n\t${foo}\n\nThis is equivalent to:\n\n\t<%= foo %>\n\nAnother example:\n\n\t{if true}\n\t\t<p>truth</p>\n\t{/if}\n\nThis is equivalent to:\n\n\t<% if(true) { %>\n\t\t<p>truth</p>\n\t<% } %>\n\nNotice the dollar sign in the ${foo} example and the lack of dollar sign in the {if} example. The syntax with the dollar sign just renders a JavaScript value.  The syntax without the dollar sign must adgere to xml-like syntax. That is, these \"tags\" must be well-formed; each open tag must have a corresponding closing tag, or they must be empty. These \"structured\" expressions are treated like functions, unless their \"tag\" name is one of if, else, while or for, in which case they are treated like control structures. For example:\n\n\t{for var i=0; i<5; i++}\n\t\t<div>Number ${i}</div>\n\t{/for}\n\nThis is a slightly more elegant way to achieve one of the previous examples.\n\n\nBasic Usage\n-----------\n\nImport the phnq_ejs module:\n\n\tvar phnq_ejs = require(\"phnq_ejs\");\n\nOr on the client just include the file.\n\nCompile your template as a string:\n\n\tvar compiled = phnq_ejs.compile(someString);\n\nThe compiled result is a string that can be eval'd to a function. For example:\n\n\tvar fn = eval(compiled);\n\nThe result of executing the function will be the template rendered into a string.\n\nExample\n-------\n\nSuppose the variable \"tmplt\" held the following string:\n\n\t<ul>\n\t\t<% for(var i=0; i<3; i++) { %>\n\t\t\t<li><%= i %></li>\n\t\t<% } %>\n\t</ul>\n\nCompile that template string as follows:\n\n\tvar compiled = phnq_ejs.compile(tmplt);\n\nTurn the compiled code into a function like this:\n\n\tvar fn = eval(compiled);\n\nRender the template by calling the function:\n\n\tvar output = fn();\n\nIn this examle, \"output\" would be the following:\n\n\t<ul>\n\t\t<li>0</li>\n\t\t<li>1</li>\n\t\t<li>2</li>\n\t</ul>\n\nParameters\n----------\n\nSuppose you have the following template in the variable \"tmplt\":\n\n\t<div>\n\t\tName: <%= user.name %><br/>\n\t\tEmail: <%= user.email %><br/>\n\t</div>\n\nWhere does the \"user\" object come from? It is not declared anywhere in the template. The answer is that information can be passed into the function that is eval's from the compiled code. For example:\n\nCompile and eval to a function:\n\n\tvar compiled = phnq_ejs.compile(tmplt);\n\tvar fn = eval(compiled);\n\nThe resulting function can optionally take a single argument, an object that represents all of the \"local\" variables that are referenced from the template.  For example:\n\n\tvar user = { name: \"Bubba Gump\", email: \"bubba@gump.com\" };\n\n\tvar output = fn({user: user});\n\nThe resulting output in this case would be:\n\n\t<div>\n\t\tName: Bubba Gump<br/>\n\t\tEmail: bubba@gump.com<br/>\n\t</div>\n\n","readmeFilename":"README.md","bugs":{"url":"https://github.com/pgostovic/phnq_ejs/issues"},"_id":"phnq_ejs@1.0.8","dist":{"shasum":"50ebdcb8220137672d16684503df3b99bb84432d","tarball":"https://registry.npmjs.org/phnq_ejs/-/phnq_ejs-1.0.8.tgz","integrity":"sha512-MBbsTmDrlOawOa1QBRQ51ruC2HFUbvbyOV3ciFuloOe3JK2ZTIbSt/iyVogC/cSHuFH5BQc8NwZzDzD0MadLeg==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIQCuabjQqibkdD0S5oKqju/8QAdqoF29uH6ytnPf1JJJXQIgT88fyU4QSwn5fjWxaLxrhe8qQe7g2xF3nXHxew7pEPA="}]},"_from":".","_npmVersion":"1.2.21","_npmUser":{"name":"pgostovic","email":"pg@phranq.com"},"maintainers":[{"name":"pgostovic","email":"pg@phnq.org"}]},"1.0.9":{"name":"phnq_ejs","description":"Embedded JavaScript templating tool","homepage":"https://github.com/pgostovic/phnq_ejs","keywords":["phnq","ejs","server","client","browser"],"author":{"name":"Patrick Gostovic","email":"pg@phnq.org"},"repository":{"type":"git","url":"git://github.com/pgostovic/phnq_ejs.git"},"main":"phnq_ejs.js","version":"1.0.9","dependencies":{"phnq_log":"1.0.x","phnq_core":"1.0.x","mocha":"1.6.0"},"scripts":{"test":"mocha -R spec"},"engines":{"node":"0.8.x"},"readme":"phnq_ejs - EJS Templates\n========================\nThe phnq_ejs module is simple templating utility that uses embedded JavaScript. It's inspired by several familiar embedded language templating systems such as ERB, JSP, ASP, etc. EJS uses the same notation as the aforementioned systems for embedding dynamic code into templates.  For example:\n\n\t<%= foo %>\n\nThis will cause the result of the statement \"foo\" to be rendered.  So, if the value of \"foo\" were \"bar\", then the following...\n\n\t<h1><%= foo %></h1>\n\n...would evaluate to:\n\n\t<h1>bar</h1>\n\nBlocks of JavaScript are embedded with the <% %> notation.  For example:\n\n\t<% for(var i=0; i<5; i++) { %>\n\t\t<div>Number <%= i %></div>\n\t<% } %>\n\nThe above code would render as follows:\n\n\t<div>Number 0</div>\n\t<div>Number 1</div>\n\t<div>Number 2</div>\n\t<div>Number 3</div>\n\t<div>Number 4</div>\n\nVery basic. Very simple.\n\nExpressions\n-----------\nAn alternate syntax, called expressions, is also available. For example:\n\n\t${foo}\n\nThis is equivalent to:\n\n\t<%= foo %>\n\nAnother example:\n\n\t{if true}\n\t\t<p>truth</p>\n\t{/if}\n\nThis is equivalent to:\n\n\t<% if(true) { %>\n\t\t<p>truth</p>\n\t<% } %>\n\nNotice the dollar sign in the ${foo} example and the lack of dollar sign in the {if} example. The syntax with the dollar sign just renders a JavaScript value.  The syntax without the dollar sign must adgere to xml-like syntax. That is, these \"tags\" must be well-formed; each open tag must have a corresponding closing tag, or they must be empty. These \"structured\" expressions are treated like functions, unless their \"tag\" name is one of if, else, while or for, in which case they are treated like control structures. For example:\n\n\t{for var i=0; i<5; i++}\n\t\t<div>Number ${i}</div>\n\t{/for}\n\nThis is a slightly more elegant way to achieve one of the previous examples.\n\n\nBasic Usage\n-----------\n\nImport the phnq_ejs module:\n\n\tvar phnq_ejs = require(\"phnq_ejs\");\n\nOr on the client just include the file.\n\nCompile your template as a string:\n\n\tvar compiled = phnq_ejs.compile(someString);\n\nThe compiled result is a string that can be eval'd to a function. For example:\n\n\tvar fn = eval(compiled);\n\nThe result of executing the function will be the template rendered into a string.\n\nExample\n-------\n\nSuppose the variable \"tmplt\" held the following string:\n\n\t<ul>\n\t\t<% for(var i=0; i<3; i++) { %>\n\t\t\t<li><%= i %></li>\n\t\t<% } %>\n\t</ul>\n\nCompile that template string as follows:\n\n\tvar compiled = phnq_ejs.compile(tmplt);\n\nTurn the compiled code into a function like this:\n\n\tvar fn = eval(compiled);\n\nRender the template by calling the function:\n\n\tvar output = fn();\n\nIn this examle, \"output\" would be the following:\n\n\t<ul>\n\t\t<li>0</li>\n\t\t<li>1</li>\n\t\t<li>2</li>\n\t</ul>\n\nParameters\n----------\n\nSuppose you have the following template in the variable \"tmplt\":\n\n\t<div>\n\t\tName: <%= user.name %><br/>\n\t\tEmail: <%= user.email %><br/>\n\t</div>\n\nWhere does the \"user\" object come from? It is not declared anywhere in the template. The answer is that information can be passed into the function that is eval's from the compiled code. For example:\n\nCompile and eval to a function:\n\n\tvar compiled = phnq_ejs.compile(tmplt);\n\tvar fn = eval(compiled);\n\nThe resulting function can optionally take a single argument, an object that represents all of the \"local\" variables that are referenced from the template.  For example:\n\n\tvar user = { name: \"Bubba Gump\", email: \"bubba@gump.com\" };\n\n\tvar output = fn({user: user});\n\nThe resulting output in this case would be:\n\n\t<div>\n\t\tName: Bubba Gump<br/>\n\t\tEmail: bubba@gump.com<br/>\n\t</div>\n\n","readmeFilename":"README.md","bugs":{"url":"https://github.com/pgostovic/phnq_ejs/issues"},"_id":"phnq_ejs@1.0.9","dist":{"shasum":"4b4ca97b3db408fa8f6f9854e8dc71ebffbfd17c","tarball":"https://registry.npmjs.org/phnq_ejs/-/phnq_ejs-1.0.9.tgz","integrity":"sha512-R57HOyr9V9OTmevtmtTjPlVPGRMQaw0S4qbLS1yyvNfkXy+9UfQ41vRe5IZgTBIFLtCjZ7MgltS6wh/YXM7gFw==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIC/t6vAd3wtjknpkeRrhpuO0IghbD42Kp7VboBj9F2C6AiEA1GkGf45ocewU62+1HgIARagRuTM7Fg5YpXRYVKLDEao="}]},"_from":".","_npmVersion":"1.2.21","_npmUser":{"name":"pgostovic","email":"pg@phranq.com"},"maintainers":[{"name":"pgostovic","email":"pg@phnq.org"}]}},"readme":"phnq_ejs - EJS Templates\n========================\nThe phnq_ejs module is simple templating utility that uses embedded JavaScript. It's inspired by several familiar embedded language templating systems such as ERB, JSP, ASP, etc. EJS uses the same notation as the aforementioned systems for embedding dynamic code into templates.  For example:\n\n\t<%= foo %>\n\nThis will cause the result of the statement \"foo\" to be rendered.  So, if the value of \"foo\" were \"bar\", then the following...\n\n\t<h1><%= foo %></h1>\n\n...would evaluate to:\n\n\t<h1>bar</h1>\n\nBlocks of JavaScript are embedded with the <% %> notation.  For example:\n\n\t<% for(var i=0; i<5; i++) { %>\n\t\t<div>Number <%= i %></div>\n\t<% } %>\n\nThe above code would render as follows:\n\n\t<div>Number 0</div>\n\t<div>Number 1</div>\n\t<div>Number 2</div>\n\t<div>Number 3</div>\n\t<div>Number 4</div>\n\nVery basic. Very simple.\n\n\nBasic Usage\n-----------\n\nImport the phnq_ejs module:\n\n\tvar phnq_ejs = require(\"phnq_ejs\");\n\nOr on the client just include the file.\n\nCompile your template as a string:\n\n\tvar compiled = phnq_ejs.compile(someString);\n\nThe compiled result is a string that can be eval'd to a function. For example:\n\n\tvar fn = eval(compiled);\n\nThe result of executing the function will be the template rendered into a string.\n\nExample\n-------\n\nSuppose the variable \"tmplt\" held the following string:\n\n\t<ul>\n\t\t<% for(var i=0; i<3; i++) { %>\n\t\t\t<li><%= i %></li>\n\t\t<% } %>\n\t</ul>\n\nCompile that template string as follows:\n\n\tvar compiled = phnq_ejs.compile(tmplt);\n\nTurn the compiled code into a function like this:\n\n\tvar fn = eval(compiled);\n\nRender the template by calling the function:\n\n\tvar output = fn();\n\nIn this examle, \"output\" would be the following:\n\n\t<ul>\n\t\t<li>0</li>\n\t\t<li>1</li>\n\t\t<li>2</li>\n\t</ul>\n\nParameters\n----------\n\nSuppose you have the following template in the variable \"tmplt\":\n\n\t<div>\n\t\tName: <%= user.name %><br/>\n\t\tEmail: <%= user.email %><br/>\n\t</div>\n\nWhere does the \"user\" object come from? It is not declared anywhere in the template. The answer is that information can be passed into the function that is eval's from the compiled code. For example:\n\nCompile and eval to a function:\n\n\tvar compiled = phnq_ejs.compile(tmplt);\n\tvar fn = eval(compiled);\n\nThe resulting function can optionally take a single argument, an object that represents all of the \"local\" variables that are referenced from the template.  For example:\n\n\tvar user = { name: \"Bubba Gump\", email: \"bubba@gump.com\" };\n\n\tvar output = fn({user: user});\n\nThe resulting output in this case would be:\n\n\t<div>\n\t\tName: Bubba Gump<br/>\n\t\tEmail: bubba@gump.com<br/>\n\t</div>\n\n","maintainers":[{"name":"pgostovic","email":"pg@phnq.org"}],"time":{"modified":"2022-06-23T21:13:43.374Z","created":"2012-06-06T00:01:25.505Z","1.0.0":"2012-06-06T00:01:26.065Z","1.0.1":"2012-10-16T19:56:21.079Z","1.0.2":"2012-10-17T20:46:46.289Z","1.0.3":"2012-10-18T15:22:38.307Z","1.0.4":"2012-10-18T19:59:05.674Z","1.0.5":"2012-10-19T14:01:18.926Z","1.0.6":"2012-10-20T15:57:18.409Z","1.0.7":"2012-10-31T01:20:12.127Z","1.0.8":"2013-05-28T17:57:17.323Z","1.0.9":"2013-06-28T17:36:21.082Z"},"author":{"name":"Patrick Gostovic","email":"pg@phnq.org"},"repository":{"type":"git","url":"git://github.com/pgostovic/phnq_ejs.git"}}