npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

grunt-knockout-templates

v0.1.0

Published

Plugin allows to replace html templates which load dynamically to a static version

Downloads

2

Readme

grunt-knockout-templates

Plugin allows to replace html templates which load dynamically to a static version. Developed for Knockout MVVM data binging.

During development it is better to have templates in separate files to avoid code duplication and allow to support your code easily.

From production perspective it is better to have all html templates in one file to avoid many requests to server and allow to render page instantly.

To use separate templates you should add the next Knockout binding:

ko.bindingHandlers['dev-template'] = {
    init: function(element, valueAccessor, allBindings, viewModel, bindingContext) {
        var value = valueAccessor();
        $(element).load(value.url, function() {
            ko.applyBindingsToDescendants(value.data || {}, element);
        });
        return {controlsDescendantBindings: true};
    },
    update: function(element, valueAccessor, allBindings, viewModel, bindingContext) {
    }
};

In this binging each template will be loaded separately and data will be applied. Html page should contains the next line:

<div data-bind="dev-template: {url: '/templates/product.html', data: product}"></div>

So, during development you will have clear code without duplicates, but code will be not optimized for a production. After running grunt task the html line below will be replaced to the source of the template surrounded with Knockout binding:

<div data-bind="with: product">
    <div data-bind="text: name"></div>
</div>

Getting Started

This plugin requires Grunt ~1.0.4

If you haven't used Grunt before, be sure to check out the Getting Started guide, as it explains how to create a Gruntfile as well as install and use Grunt plugins. Once you're familiar with that process, you may install this plugin with this command:

npm install grunt-knockout-templates --save-dev

Once the plugin has been installed, it may be enabled inside your Gruntfile with this line of JavaScript:

grunt.loadNpmTasks('grunt-knockout-templates');

The "knockout_templates" task

Overview

In your project's Gruntfile, add a section named knockout_templates to the data object passed into grunt.initConfig().

grunt.initConfig({
  knockout_templates: {    
    your_target: {
      src: ['pages/**.html']
    },
  },
});

where src is a lit of the pages which contains templates definitions.

Release History

0.1.0 - initial version