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 🙏

© 2026 – Pkg Stats / Ryan Hefner

dust-react-helper

v2.0.0-beta1

Published

Helper to render React component in DustJS template

Downloads

15

Readme

dust-react-helper

A convenient helper for server-side rendering React components from within DustJS templates. At the moment it's only tested with the Linkedin version of Dust.

Installation

npm install dust-react-helper

And just need to set it up with:

var dust = require('dustjs-linkedin');
require('dust-react-helper').install(dust);

If you're using JSX syntax without prior compilation, include babel Require Hook or node-jsx before installing the helper:

require('babel/register'); // or
require('node-jsx').install()

Usage

The module registers a new @react helper. You can call it directly in your Dust template like so:

{@react component="./react/my_component" /}

The component path is relative to the directory where you run your node server. There's also a way to set the React component directory globally:

var helper = require('dust-react-helper');
helper.setReactDir('react');

And then the helper will pick up components relative to the configured react directory:

{@react component="my_component" /}

If you want to pass some paramaters to the component:

{@react component="my_component" param1=param1 param2="spoon" param3="{param3}" component="param_component" /}

Internal cache

React.renderToString is slow compared to the rest of Dust. dust-react-helper contains an internal cache to store pre-transformed versions of the helper nodes using Memoizee.

You can pass the paramaters when you install dust-react-helper:

var dust = require('dustjs-linkedin');
require('dust-react-helper').install(dust, undefined, {max: 2000});

{ max: 2000, primitive: true } will set the maximum number of cached jsx nodes to 2000. { maxAge: 1000, primitive: true } will set the maximum age to 1000 ms (one second)

You can clear the internal cache like this:

var dust = require('dustjs-linkedin');
var helper = require('dust-react-helper');
helper.install(dust, undefined, {max: 2000});
helper.clearCache();

======= The primitive: true tells the cache to generate a hash out of the properties. If you are sending large JSON objects as paramaters, the cache can get confused. If you remove that, it's about as fast as no cache at all. You can locally remove the cache (useful if you are generating forms on the server side) with noCache=true inside of the dust helper like this:

{@react component="./react/my_component.jsx" noCache=true /}

Thanks @wirehead for the great contribution!