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

uniserval

v1.0.1

Published

Use Server Side Rendering Anywhere.

Downloads

4

Readme

Version Github License CI Testing Maintainability

Universal Server Side Rendering (SSR)

Use Server Side Rendering (SSR) everywhere.

Inspired from tossr.

Features

  • Typescript support.
  • Ease of Integration. You can integrate it with Golang, Rust, Java, PHP and etc via HTTP Server or Child Process. (On Progress)
  • Can be used with Vanilla JS, jQuery, Svelte, Routify, Handlebars and etc.
  • Can be used in Lambda Functions (or Serverless) like AWS Lambda, Netlify, Vercel and etc. (NodeJS v10 or newer required.)
  • Passing custom Props like cookie, session and etc to Javascript Code. (We avoid to use meta element for temporary state or data to increase performance. Assigning data to window object is faster than create new meta element and append it into DOM.)

Installation

We don't need any special template. Just install the uniserval library with your package manager:

yarn add uniserval
# or
npm i uniserval

Usage

Using Express JS (Node JS)

const express = require('express')
const { readFileSync } = require('fs')
const { renderToString } = require('uniserval')

const template = readFileSync('./public/template.html', 'utf8')
const script = readFileSync('./public/script.js', 'utf8')

const server = express()

server.use((req, res) => {
  renderToString(
    template,
    script,
    {
      // Put in here the data you want to access it from Javascript code.
      // You can access the data in `window.serverProps`.

      // Example:
      pageTitle: `Now you're in: ${req.path}`,
    },
    {
      path: req.path,
    }
  )
    .then((stringHtml) => {
      res.send(stringHtml)
    })
    .catch((error) => {
      // Handle error in here
    })
})

server.listen(3000)

API

renderToString(html, script, serverProps, options)

Description

Render HTML & Javascript code to string.

Arguments

  • html - HTML string that will be processed.
  • script - Javascript code that will be executed.
  • serverProps - Custom data that will be passed to script code. The data can be accessed from window.serverProps.
  • serverPropsFieldName - Don't want to use the name serverProps? you can replace it with another name. Example serverData, initialData, etc.
  • options - Configuration
    • host - Hostname to use while rendering process. Default: http://jsdom.jss (You can use anything. But make sure to use the valid Hostname. localhost is an invalid instance.)
    • path - Will be used for window.location.pathname.
    • eventName - If exists, the output HTML string will be returned after event emitted. If not, it will be returned immediately.
    • userAgent - userAgent affects the value read from navigator.userAgent, as well as the User-Agent header sent while fetching sub-resources. See W3Schools userAgent.
    • cookie - Will be used for document.cookie. See document.cookie documentation.
    • beforeEval : (dom) => void - a Function that will be called before the script is executed.
    • afterEval : (dom) => void - like beforeEval, but it will be called after the script executed.

TODO

  • Add JSDOC
  • Add more explanation in README.md
  • Create CLI version
  • Create HTTP Server version
  • Make more examples

Note

If you find an problem, please report it on the Issue page. or If you have an suggestion and enhancement, please create the Pull Request. We will discuss it first.

Need more example to use uniserval? try visiting the example folder.

Thanks.