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

dist-bundler

v0.5.0

Published

Combines built code in a directory to a single .js file.

Downloads

15

Readme

Build and test

dist-bundler

Combines built code in a directory to a single .js file.

Installing

npm install --save-dev dist-bundler

Building and testing

This tool is built with typescript. In order to create a build run:

npm run build

This will clean up and create a new build in build/. The command also copies relevant resources into the build/ folder.

When developing you can run the watch command in order to continously build the project when code is changed:

npm run watch

In order to run tests the project needs to be built, then you can run the test command:

npm test

Usage

When run the tool will dig through all files and sub folders in a given directory and combine all .js and .css files into a single .js file which loads all relevant files from a generated folder with scripts. The structure will look like this:

build/
├─ static/
│  ├─ some-styling.css
│  ├─ some-javascript.js
│  ├─ some-polyfill.js
├─ boot.js

Configuration of where files will be collected from and where they will be outputted can be set in ./config.json. The default configuration looks like this:

{
  "copyTasks": {
    "js": {
      "source": "dist/js/",
      "target": "js/"
    },
    "styles": {
      "source": "dist/styles/",
      "target": "styles/"
    }
  },
  "outputFolder": "build/"
}

copyTasks: Defines where to copy files from.

  • js: Defines source and target directory for .js files.
  • css: Defines source and target directory for .css files. outputFolder: Where the resulting files should be put.