Research
Security News
Threat Actor Exposes Playbook for Exploiting npm to Build Blockchain-Powered Botnets
A threat actor's playbook for exploiting the npm ecosystem was exposed on the dark web, detailing how to build a blockchain-powered botnet.
grunt-contrib-templify
Advanced tools
A simple project for quick and dirty conversion of HTML files to javascript for various cases, particularly unit testing.
Quick and dirty HTML to Javascript strings
This project is designed to be a quick and simple solution to converting HTML files to templates in javascript under various conditions.
This was started specifically to fill a need for unit tests to get HTML templates in angular and make them available for use in Jasmine tests with Angular V1. As such the initial versions of this project will center around that process.
This project is designed for use with Grunt. If you don't already have it installed:
npm install grunt --save-dev
To get this project added:
npm install grunt-contrib-templify --save-dev
Then inside your grunt file you'll need to add a line to load this project:
templify: {
// ...
}
Then configure the templify task in your grunt configuration (See below).
Task targets, files and options may be specified according to the grunt Configuring tasks guide.
Below is a general description of what the task is doing referenced by the various supported "modes"
The task creates a function that handles binding a beforeEach clause that adds the templates to a global template variable. The equivalent code for __templifyTemplates as an example:
var __templates = {};
beforeEach( function($templateCache) {
__templates["..."] = "...";
__templates["..."] = "...";
// ...
} );
The task creates a function that simply binds the templates to the $templateCache. The generated function for __templifyTemplates as an example:
function($templateCache) {
$templateCache.put("...", "...");
$templateCache.put("...", "...");
// ...
};
The task creates a Vue Plugin to provide the HTML files as templates:
var Templify = {};
Templify.install = function(Vue, options) {
Vue.templified = function(name) {
switch(name) {
case "[Filename]": return [Template];
//...
default: return undefined;
}
};
};
To use the Plugin, your code will have to call
Vue.use(Templify);
And then your components should be able to access their templates:
Vue.component("example", {
// ...
"template": Vue.templified("[Filename]")
});
The Vue plugin accepts several option parameters as well
Type: String
Default: 'templified'
Sets the name of the method off of Vue
where the templates are amde available.
The task creates a function that handles binding a beforeEach clause that adds the templates to the $templateCache. The equivalent code for __templifyTemplates as an example:
beforeEach( inject( function($templateCache) {
$templateCache.put("...", "...");
$templateCache.put("...", "...");
// ...
} ) );
Type: String
Optional
Specifies the root directory for scanning files and writing output files. Useful when using abstract layers such as mocha or PM2.
Type: Array
This is an array of objects that describe how to process a directory. Each directory can be passed options for how to build the template.
Type: String
The path to the folder where the templates are currently located
Type: Function(String, Object)
Optional
This function is passed the current path to the template and is expected to return the name to use for the template, which by default is merely the current path. This options allos the name to programmatically created based on the path to the template.
The second argument is the current directory object templates[] for further manipulation if desired.
Type: String
Currently unused. Future use to allow separation of templates to be declared into their respective angular modules.
Type: String
Currently unused. Future use to specify text to trim from the begining or end of the path. This is more accurately accomplished with templates[].rewrite.
Type: String
Currently unused. Future use to apply a simple prefix to the template name. This is more accurately accomplished with templates[].rewrite.
Type: String
Currently unused. Future use to apply a simple suffix to the template name. This is more accurately accomplished with templates[].rewrite.
Type: String
Indicates how the output file should be written, specifically it indicates what builder to use when processing the template cache creation.
Type: String
Indicates where to output the javascript.
This is currently being written to quickly fill a specific issue of getting HTML templates into Jasmine tests for Angular while using Karma without too much craziness.
The current process is designed to be simple but not as smooth as desired. Initially the Grunt configuration needs to be put in place:
templify: {
testing: {
templates: [{
path: "templates/",
rewrite: function(path) {
return path.substring(path.lastIndexOf("/") + 1);
}
}],
suffixes: [".html"],
mode: "karma-angular",
output: "specs/templates.js"
}
}
(Note: that "testing" is an arbitrary label)
Once the grunt process is described, the templify:testing task will need to preceed the karma task for testing. The idea being that the generated javascript file will then be provided to karma, where the declarations for the templates to pass to angular are ready in a function named __templifyTemplates. Then inside the jasmine tests.
In Karma's Grunt declaration:
karma: {
options: {
// ...
files: [
// Dependencies...
"specs/templates.js",
// Tests...
]
},
// ...
}
In your Jasmine tests:
// ...
/* Creates a beforeEach clause in Jasmine to bind the templates to the Template cache */
__templifyTemplates();
// ...
Now when using angular later, the templates can be pulled from the $templateCache for use in unit and functional tests.
For Example:
describe("Templify Karma-Angular template processing", function() {
var $compile, $scope;
var template, html, element;
__templifyTemplates();
describe("Templating", function() {
beforeEach(inject(function(_$compile_, _$rootScope_) {
$compile = _$compile_;
$scope = _$rootScope_.$new();
}));
it("passes standard checks", inject(function($templateCache) {
$scope.title = "Titling";
$scope.paragraph = "This is some text";
template = $compile($templateCache.get("angular-template1.html"))($scope);
$scope.$digest();
html = template.html();
expect(html).toContain($scope.title);
expect(html).toContain($scope.paragraph);
expect(html).not.toContain("title");
expect(html).not.toContain("paragraph");
}));
});
});
FAQs
A simple project for quick and dirty conversion of HTML files to javascript for various cases, particularly unit testing.
The npm package grunt-contrib-templify receives a total of 0 weekly downloads. As such, grunt-contrib-templify popularity was classified as not popular.
We found that grunt-contrib-templify demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Research
Security News
A threat actor's playbook for exploiting the npm ecosystem was exposed on the dark web, detailing how to build a blockchain-powered botnet.
Security News
NVD’s backlog surpasses 20,000 CVEs as analysis slows and NIST announces new system updates to address ongoing delays.
Security News
Research
A malicious npm package disguised as a WhatsApp client is exploiting authentication flows with a remote kill switch to exfiltrate data and destroy files.