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

webrender

v2.2.1

Published

Run live web and build static site using pure HTML/JS/CSS, with PostCSS, Rollup

Downloads

5

Readme

webrender

Run live web and build static site

NPM Build Status Coverage Status

Usage

Suppose that we want to build a front-end only website with pure HTML/CSS/JS or React, Vue, whatever. Our repo may look like following folder structure:

my-project
 - package.json
 - src/
     - assets
          - css
              - main.css
              - theme.css
          - js
              - main.js
              - another-modules.js
     - static
        - fonts
        - images
        - favicon.ico
     - templates
       - index.html
       - about.html
       - faq.html
     - config.json

Here the website source code is placed within src folder. However the folder name can be anything else. templates dir is not required. If it does exist, webrender will try to parse them with nunjucks template engine. Otherwise, the HTML files located at root folder will be used.

View examples/ for reference.

In order to use webrender, let's install it:

npm i webrender

Then you can use it with command line or call it from code.

Command Line

Add these 2 commands to script section of the package.json file, for example:

  "scripts": {
    "run": "DEBUG=webrender:* webren run ./src",
    "build": "DEBUG=webrender:* webren build ./src ./dist"
  },

Since now, we can run the website within src folder to view and develop it as below:

npm run dev

Once everything is ok, we can build a static site into dist folder:

npm run build

Programmatically

Run a website located at ./src folder:

const run = require('webrender/scripts/run');
run('./src');

This approach is helpful to work with nodemon for auto reloading.

  "scripts": {
    "dev": "DEBUG=webrender:* PORT=4728 nodemon server.js -e js,css,html,json,yaml"
  },

You can even add more express middlewares:

const path = require('path');

const cors = require('cors');
const favicon = require('serve-favicon');

const middlewares = [
  cors(),
  favicon(path.join(__dirname, 'public', 'favicon.ico')),
];

run('./src', middlewares);

Lastly, just build static version of this website to ./dist folder:

const build = require('webrender/scripts/build');
build('./src', './dist');

Test

git clone [email protected]:ndaidong/webrender.git
cd webrender
npm i
npm test

License

The MIT License (MIT)