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

ender-swig

v0.12.0

Published

Ender port of Swig (fast django-like templating engine for node.js and browsers)

Downloads

12

Readme

Swig for Ender

Swig is a fast template engine inspired by django-t (also known as Twig for Symfony's users).

It's written by Paul Armstrong and can be found here.

Installation

If you don't already have installed Ender, go get it! Now. It's good for you.

$ sudo npm install ender -g

Then make your build with Swig included:

$ ender build ... ender-swig

Or add it to an existing build:

$ ender add ender-swig

You could ask yourself "Why the fuck should I type add ender-swig and not simply add swig ?". It's a good question:

  • First, the swig module you'll find in npm repository is not fully browser-compatible, it will include the node version to your build. Not cool for your Ender build.
  • The clean way is to call make browser from Swig repository, then build this into ender. That's what this module has made for you.
  • Note that I may find a way using a properly written ender.js to make it ender-ready, and then I'll make a Pull Request to original repository. You'll know when it happens because there will be a huge warning in front of this README.

Usage

This module adds a $.render method, and a $.swig object.

$.swig is a simple copy of the swig object. See Swig's documentation for more information.

The render method adds some magic to ease integration of inline templates (in <script> tags):

Simple rendering

You can call $.render(id, [vars]) to render an inline template. The module will take care of retrieving content and pre-compiling it for you.

<script type="text/html" id="tpl">
Hello, {{ name }}.
</script>
console.log($.render('tpl', {"name": "dude"}))
// Hello, dude.

Support for inheritance

In this example, note that you didn't have to compile parent template. In a normal situation you would have had to, but the module detects extensions and tries to compile associated inline template.

<script type="text/html" id="parent">
Hello, {% block name %}John Doe{% endblock %}.
</script>
<script type="text/html" id="child">
{% extends 'parent' %}
{% block name %}dude{% endblock %}
</script>
console.log($.render('child'))
// Hello, dude.

Support for strings

You can also render templates directly from strings, but you'll then have to provide a fake filename by passing a third parameter to $.render.

<script type="text/html" id="child">
{% extends 'parent' %}
{% block name %}dude{% endblock %}
</script>
// compile parent from string
$.render('Hello, {% block name %}John Doe{% endblock %}.', {}, 'parent')
// compile child from inline template
console.log($.render('child'))
// Hello, dude.