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

residual

v0.1.2

Published

Lightweight framework (Node/browser)

Downloads

3

Readme

Residual - lightweight framework (Node/browser)

This module is experimental, use at your own risk.

Features/principles:

  • Renderers defined by returning inner HTML (in a Promise) for element
    • chosen by URI Template and CSS selector
      • only tag-names, classes and IDs are supported for now
    • partial renders - nest another URL (or just a child property) in an element
    • server-side: render static page as HTML
    • client-side: synchronise DOM (using partial renders)
  • Page router
    • based on URI Templates
    • each page corresponds to one resource URL (GET)
      • For more complex views, define a custom resource URI scheme, e.g. diff:{A}:{B}
    • other methods (POST/etc.) are "actions" - handlers can redirect display to new URL when finished
    • hashes resolve against the rest of the URL (compatibility with
      • e.g. /foo/bar#/xyz is interpreted as /xyz for the purposes of the router. If your route has an actual fragment in it, this will be translated into a double-hash, e.g. /foo/bar##/subProp.
  • Generate self-contained bundle including config/renderers
    • small: ~12KB minified / ~5KB gzipped (plus user-supplied config/renderers)
    • only works if all config functions have no closure variables
  • Requires ES5 (throws immediately otherwise)
    • IE8 and below can just cope with the server-side version

Usage

var engine = require('residual')();
// URL map defined in priority order
engine.map('/json/home', '/');
engine.map('/json/{+url}', '/html/{+url}');
// Define renderer
engine.register('{+url}', '.raw-json', function (url, data, web) {
	return '<pre>' + web.escape(JSON.stringify(data)) + '</pre>';
});

// Server-side: get HTML for resource
engine.html('/json', 'body.raw-json').then(function (html) {
	var pageHtml = '<html><body class="raw-json">' + html + '</body></html>';
});

// Client-side - fill individual element
engine.fill(document.body, '/json/home');

// Client-side - fill page (title and body) based on uri
engine.start();

// Generate standalone client code with the above config (assuming no closure variables used)
var jsCode = engine.clientCode();
fs.writeFileSync('static/bundle.js', jsCode); // ready to minify

Minifying

When minifying, properties starting with m_ are safe to be mangled. Here is an example use of UglifyJS:

uglifyjs bundle.js --mangle --mangle-props --mangle-regex /^m_/ --output residual.min.js --source-map residual.js.map
// In Node
var clientCode = display.clientCode();
fs.writeFileSync('bundle.js', clientCode);
var minified = require('uglify-js').minify('bundle.js', {
	mangle: true,
	mangleProperties: {regex: /^m_/},
	outSourceMap: 'bundle.js.map'
});
fs.writeFileSync('bundle.min.js', minified.code);
fs.writeFileSync('bundle.js.map', minified.map);