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

havana-component-renderer

v0.1.0

Published

A component renderer

Downloads

5

Readme

Havana component renderer

Build Status Dependency status

A component renderer.

Havana component renderer works with an HTML response handler such as Havana component compiler or a library with an interchangeable API. When a component compiler publishes a component.render event Havana component renderer will use the Fetch API to retrieve the component template (the endpoint is worked out from the root URL, component directory and template pattern passed in on instantiation plus the component name). Havana component renderer will then compile the template using the compiler function passed in on instantiation (i.e. mustache.compile). The compiler function is expected to return a function, which is then invoked with the component's properties object. An HTML string is returned and published by Havana component renderer in a component.rendered event.

How to install

npm install havana-component-renderer

How to use

import ComponentCompiler from 'havana-component-compiler';
import ComponentHandler from 'havana-component-handler';
import ComponentRenderer from 'havana-component-renderer';
import Event from 'havana-event';
import Router from 'havana-router';
import Server from 'havana-server';
import Static from 'havana-static';

import handlebars from 'handlebars';

const event = new Event();

const port = 3000;

const reporting = {
  'level': 2, 
  'reporter': console.log,
};

const server = new Server({
  'event': event,
  'reporting': reporting,
});

new Static({
  'event': event,
  'reporting': reporting,
  'rootDir': __dirname,
  'staticDir': 'public',
});

new Router({
  'event': event,
  'reporting': reporting,
  'routes': [
    {
      'url': '/',
      'method': 'GET',
      'components': [
        {
          'component': 'page',
          'properties': {
            'content': 'Hello world',
          },
        },
      ],
    },
  ],
});

new ComponentCompiler({
  'event': event,
  'reporting': reporting,
});

new ComponentRenderer({
  'compiler': handlebars.compile,
  'componentDir': 'component',
  'event': event,
  'reporting': reporting,
  'rootURL': `http://localhost:${port}`,
  'templatePattern': ':name/template/:name.hbs',
});

new ComponentHandler({
  'event': event,
  'reporting': reporting,
});

server.listen( port );

The above will expect the following directory structure:

— server.js
— public
  — component
    — page
      — template
        — page.hbs

Event list

Events take the form of Havana event or a library with an interchangeable API.

Publish

  • component.rendered: Signifies that a component has been rendered into an HTML string for consumption by a component compiler.

Subscribe

  • component.render: Allows a component compiler to notify Havana component renderer that it requires a component object rendered to an HTML string.

ES2015+

Havana component renderer is written using ES2015+ syntax.

However, by default this module will use an ES5 compatible file that has been compiled using Babel.

In the dist directory there are four files, the default is renderer.server.js. The default when using a client-side bundler that supports the browser field spec is renderer.browser.js.

Havana component renderer currently requires the Babel polyfill. You are expected to supply this yourself. However, as a courtesy you will also find renderer.server.with-polyfill.js and renderer.browser.with-polyfill.js in the dist directory.