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

mithril-export

v0.1.2

Published

Append self contained mithril views to normal DOM elements

Downloads

5

Readme

mithril-export

Travis

Append self contained mithril views to normal DOM elements

install

$ npm install mithril-export --save

usage without

Take this simple mithril module that is to be packaged with browserify:

var EventEmitter = require('events').EventEmitter
var m = require('mithril')

function Dashboard(config){
	var dashboard = new EventEmitter()

	dashboard.vm = {}

	dashboard.controller = function() {
	    dashboard.vm.greeting = "Hello";
	};

	dashboard.view = function(vm) {
	    return m("h1", dashboard.vm.greeting);
	};
}

module.exports = Dashboard

Then in our app - we need a way of adding this widget to the page:

var Dashboard = require('./dashboard')
var m = require('mithril')

var dashboard = Dashboard({
	summary:true
})

m.module(document.body, dashboard);

But this requires the top level app to know about mithril and reduces the dashboard modules portability to other applications that want to use it but have not installed mithril.

usage with

Using mithril-export we create a utility render function to hide mithril from the top level app:

var EventEmitter = require('events').EventEmitter
var m = require('mithril')
var mexport = require('mithril-export')

function Dashboard(config){
	var dashboard = new EventEmitter()

	var vm = {}

	dashboard.controller = function() {
	    vm.greeting = "Hello";
	};

	dashboard.view = function(vm) {
		return m("h1", vm.greeting);
	};

	// here we choose mexport.module or mexport.render
	// depending on if the component is auto-updating
	dashboard.render = mexport(dashboard)

	return dashboard
}

module.exports = Dashboard

And now the top level app just uses the modules api without knowing about mithril:

var Dashboard = require('./dashboard')

var dashboard = Dashboard({
	summary:true
})

dashboard.render(document.body)

api

var fn = mexport(mithrilModule)

Generate a function that will render a mithril module to the passed DOM element.

A mithril module is an object that has both controller and view properties.

var fn = mexport.render(component)

The same as the module method but that calls the mithril render method which only draws once.

license

MIT