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

django-express

v1.0.0

Published

A wrapper of Django's template engine for Express.js

Downloads

20

Readme

django

NPM version Downloads Build Status Build status Dependency Status Dev Dependency Status Build Status Coverage Status Build with Grunt

💥 django on npm is deprecated cause it's a trade mark, we now publish to django-express instead.

A wrapper of Django's template engine for Express.js.It's designed only for development on web front-end side.DO NOT use it for production.

Django's template syntax is quite different from twig,jinja2 or swig.For now,there is no replacement like django.js can simulate the syntax and the interfaces.But we can make Django itself working with node.js,even Express.js.So a wrapper is required.

I setup a node-python bridge through standard in/out stream.It can handle with any size of mock data or source template file theoretically.The shell script below shows how it works:

#echo '{"name":"django"}' | python django.py ./templates index.html

install

First you have to install Django framework, pip or easy_install is recommended:

# pip install -v Django==1.7
//or
# easy_install "Django==1.7"

Make sure it's installed successfully.

Set django as a template engine for Express.js:

var express = require('express');
var path = require('path');
var django = require('django');

django.configure({
    template_dirs: path.join(__dirname, 'template')
});

var app = express();

app.engine('html', django.renderFile);
app.set('views', path.join(__dirname, 'template'));
app.set('view engine', 'html');

API

1.configure(configurations)
  • param configurations: [Object][Required] the configurations object
  • since 0.1.0
  • return this

Set the configurations.It should be called at first.

2.renderFile(tpl, data, callback)
  • param tpl: [String][Required] template file name
  • param data: [Object][Optional] plain object to render a template
  • param callback: [Function][Required] render callback function
  • since 0.1.0
  • return undefined

Render a template file with data.

3.render(source, data, callback)
  • param source: [String][Required] template source codes
  • param data: [Object][Optional] plain object to render a template
  • param callback: [Function][Required] render callback function
  • since 0.4.0
  • return undefined

Render a block of source codes with data.

configurations

All the following configurations should be set by configure function.

1.template_dirs
  • Type: [String]
  • Default: 'templates'

The root directory of the template files,this is necessary when templates extend or include.It could be an array in the future.

notice

  • only utf8 encoding is supported

author

licence

MIT