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

morfine

v1.2.0

Published

Pure, stateless wrapper around nanomorph

Downloads

1

Readme

morfine

Pure, stateless wrapper around nanomorph.

Installation

npm i morfine

Usage

var morfine = require('morfine')
var html = require('nanohtml')

window.text = 'hello'

function render () {
  return html`
    <div>
      <a href="#">${window.text}</a>
    </div>
  `
}

var wrapper = morfine(render)
document.body.appendChild(wrapper.el)

// attach optional lifecycle methods
wrapper.beforerender = function (el) {
  console.log(el, ' will be rendered')
}
wrapper.afterrender = function (el) {
  console.log(el, ' was rerendered')
}

// attach the function to window for testing purposes
window.rerender = wrapper.rerender

API

wrapper = morfine(renderer[, beforerender, afterrender])

Takes a renderer function that returns a Node (manually defined or from nanohtml for example). Optionally you can set the lifecycle methods here. You must do this if calling afterrender on the first render is needed. Returns a wrapper object.

wrapper.el

The Node itself. This is what you add to the body.

wrapper.rerender()

Calls the renderer again and morphs the DOM.

wrapper.r()

Alias for wrapper.rerender()

wrapper.beforerender(el)

Optional lifecycle method. Called after the new tree has been generated, but before the wrapper update. You can directly access and modify el.

wrapper.afterrender(el)

Optional lifecycle method. Called after the wrapper has been updated. You can directly access and modify el, the current element in the DOM.

Note: nanocomponent uses the afterupdate name instead of afterrender, but in this case we always try to update, so let's stick to render.

Why?

Similar to what I've tried to achieve in bik, using the power of nanomorph on the lowest level possible in a non-Choo environment. Plus lifecycle methods, because they might come handy.

See Also