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

combynexpress

v3.0.0

Published

Combyne view engine for Express.

Downloads

1,328

Readme

CombynExpress

View engine support for Combyne

Build Status

Created by Tim Branyen @tbranyen

Installing.

npm install combynexpress

Requiring.

var combynExpress = require("combynexpress");

Registering with Express.

Note: The lookup folder name is views and it is relative to your working directory.

app.engine("combyne", combynExpress());
app.set("view engine", "combyne");

If you prefer a different extension (not .combyne) you can easily change:

app.engine("html", combynExpress());
app.set("view engine", "html");

You can set certain options during the invocation by passing an object:

app.engine("combyne", combynExpress({ filtersDir: "filterz" }));
app.set("view engine", "combyne");

Changing Combyne settings.

You can change internal settings to Combyne through the exposed settings property:

combynexpress.settings.delimiters = {};

Working with partials.

Within Express, all Combyne partials are mapped to views. This allows you to trivially load from a partials directory like:

{%partial partials/my-partial %}

This would then map to the customized views directory and load partials/my-partial from there.

Working with injected partials.

While using Express it's often desired to wrap a page template with a layout.

An example layout:

<body>{%partial body%}</body>

A page template that looks like this:

{%extend layout as body%}
Hello world
{%endextend%}

This will automatically fetch the layout view and render the page template within the body partial.

Registering global partials.

You can register global partials:

var combynExpress = require("combynexpress");

// Assign a basic partial.
combynExpress.registerPartial("global", {
  render: function() { return "global"; }
});

Global partial naming will override any local partials and not incur a filesystem hit.

Working with filters.

Within Express, all Combyne filters are mapped to files. This allows you to trivially load from a filters directory like:

{{ prop|my-filter }}

This will require the filter functions and register them onto the template. In the above example it would look for filters/my-filter.js in the configured views directory. You can change the directory to search for templates in:

combynExpress.settings.filtersDir = "some-other-folder";

Registering global filters.

You can register global filters:

// Assign a basic identity filter.
combynExpress.registerFilter("my-global-filter", function(value) {
  return value;
});

Global filter naming will override any local filters and not incur a filesystem hit.