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

set-page

v3.0.1

Published

Framework agnostic, isomorphic `<html>`, `<body` and `<head>` rendering utility.

Downloads

8

Readme

Formerly named set-head.

Framework agnostic, isomorphic <html>, <body and <head> rendering utility.

Installation

npm install set-page

Example

import Page from 'set-page'

// Create a new page element, this should be done once per request.
const page = new Page()

page
  // Set html and body attributes.
  .html({ lang: 'en' })
  .body({ class: 'loading' })
  // Add elements to <head> via method chaining.
  .meta({ charset: 'utf8' })
  .title('My App')
  .base({ href: '/admin/' })
  .meta({ name: 'description' content: 'Cool stuff' })
  .link({ rel: 'stylesheet', href: 'index.css' })
  .script({ async: true, src: 'index.js' })

Overriding

set-page makes overriding values easy. If you invoke page again later it will replace any existing similar head element and merge any body or html attributes.

The module uses special keying scheme for head elements found in ./src/base.js under const KEYS to understand which elements to replace and which to add. Ultimately this allows for efficient re-ordering and rendering without any 'key' non-sense.

// Setting defaults somewhere (perhaps in a middleware or plugin.)
page
  .title('My App')
  .meta({ name: 'author', content: 'Dylan Piercey' })
  .meta({ name: 'description', content: 'Welcome to the site' })
  .link({ rel: 'stylesheet', href: '/app.css' })
  .script({ async: true, src: '/app.js' })

// The later in a specific route you can continue chaining like so to override.
page
  .title('My App > My sub page')
  .meta({ name: 'description', content: 'Sub page description' })

Browser Rendering

To render to the browser, simply invoke 'render' after all setting up the page.

page.render()

Server Rendering

Server side rendering is accomplished by invoking renderToString after setting up the page.

export default (req, res) => {
  const parts = page.renderToString()
  res.end(`
    <!doctype html>
    <html${parts.htmlAttributes}>
      <head>${parts.head}</head>
      <body${parts.bodyAttributes}>
        ...
      </body>
    </html>
  `)
}

Contributions

  • Use npm test to run tests.

Please feel free to create a PR!