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

wbpk

v0.0.3

Published

Programmatic interface to webpack similar to Gulp

Downloads

1

Readme

WBPK

Use webpack in a more programmatic way.

Usage

Create a wbpk.js file in your root directory.

// wbpk.js
var wbpk = require('wbpk').default;

var instance = new wbpk();

instance
.entry(__dirname + '/src/app.js')
.output(__dirname + '/dist/bundle.js')
.loaders([
    {
        test: /\.js$/,
        loader: 'babel-loader'
    }
])
.run(); // can also use .watch()

Then run wbpk to build / watch.

API

.config(config: object|string)

Load a pre-exisitng webpack config. Can be an object or a path to a webpack.config.js.

.entry(path: string|array)

Your entry point. Can be a string or an array of file paths. All files must be absolute (append __dirname).

.output(path: string)

Your files destination. Pass the whole filepath to where you want your build to go, including the filename and extension.

.loaders(loaders: object[])

What loaders to use. Right now these should be the same as you would pass to your webpack config. Know of a way to make this more user-friendly? Submit an issue or pull request.

.run()

Executes webpack to build based off of your config.

.watch(opts: object)

Tells webpack to watch for changes based on your config. All valid webpack watch config options can be passed here.