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

jscaffold-template-webpack

v2.0.0

Published

jscaffold template with webpack

Downloads

2

Readme

jscaffold-template-webpack

What?

This is a jscaffold template with webpack. You can use this with vue, react and so on.

Why?

In some spa projects, we build all the source files into one js file, thus the browser would load slowly. And some times there are many entries in hybird app according to different spa router.

How?

So we need to split code into modules, and load them asynchronously.

We split code with require.ensure, build with command npm run build, so we get dist directory.

In thie directory:

  • vinfo.json

    eg:

    {
      "buildHash": "235b576d1f7ba5d42ee4",
      "buildDate": "12/6/2016, 7:14:30 PM",
      "buildVersion": "v1.0.0",
      "buildNumber": "20161107v1",
      'cache': true,
      "moduleList": [
      	{
      		"name": "load",
      		"hash": "be311daea3cecaaca032",
      		"type": "js"
      	},
      	{
      		"name": "baselib",
      		"hash": "936321dc7394e195df36",
      		"type": "js"
      	},
      	{
      		"name": "app",
      		"hash": "5069bbe8821e4ba61b7b",
      		"type": "js"
      	}
      ],
      "ios": {
          "buildVersion": "v1.1.0",
          "moduleList": [
              {
                  "name": "load",
                  "hash": "ajsdflkjasdlfjaskdjf",
                  "type": "js"
              }
          ]
      },
      "other": {
          "moduleList": [
              {   
                  "name": "load",
                  "hash": "ajsdflkjasdlfjaskdjf",
                  "type": "js"
              }
          ]
      }
    }

    This json file describes build info.

    • buildVersion This is important. Builded according to src/config.js (the version pattern).
    • buildNumber This is build number (GNU version style).
    • cache This tells to store base modules in localStorage and load them from next time. Remove "--cache" from package.json will load base modules always from server.
    • moduleList This is the default base modules need to load in the browser in sequence.
    • ios This specifys ios devices modules loaded.
    • android This specifys android devices modules loaded.
    • other This specifys other runtime modules loaded.

    Especially, the module config in ios|android|other will override the default one.

  • index.html This will load modules in vinfo.json in seqence. In the root directory, file index.html is the template of this.

All other files will be placed in the version directory.

  • File load is webpack loader, which webpack modules load info is in it.
  • File baselib is the base library used in project. eg: vue, chartjs...
  • File app is the project main file.
  • File buildNumber.json is a build history.
  • Other asynchronous modules will be placed in modules directory with their names.