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

@bucky24/builder

v0.3.0

Published

This is a simple wrapper around the webpack hot-reload system. Why build this? Well I've found the following issues with the webpack hot reload system:

Downloads

6

Readme

@bucky24/builder

This is a simple wrapper around the webpack hot-reload system. Why build this? Well I've found the following issues with the webpack hot reload system:

  • Doesn't handle complex paths well. Try to load localhost:8080/a/long/path/here. Webpack dev server will attempt to find build/a/long/path/here/bundle.js which obviously doesn't exist.
  • If you're building a server and client, you have to run them both as separate node processes if you're using the webpack dev server.

This module allows you to easily start a webpack dev server that hot reloads appropriately and integrates with your existing backend. Are there better modules that do this already? Yeah probably, but that's never stopped me before.

Usage

Builder

This module exports a single class, Builder, as a default export.

Constructor

The constructor takes a single argument, that being the pathname to the webpack config you want to use.

const Builder = require('@bucky24/builder');
const path = require('path');

const builder = new Builder(path.join(__dirname, 'webpack.config.js'));

serveIndex

This method serves the built index html file from the build directory. It takes as a parameter an express Response object

app.get('/', async (req, res) => {
    builder.serveIndex(res);
});

serveStatic

This method attempts to extrapolate what static resource is being requested, and serve it from the build directory. It takes as parameters an express Request object and an express Response object.

app.get("*", (req, res) => {
    builder.serveStatic(req, res);
});

setServer

This method allows the Builder to listen for websocket requests and connect the hot-reload socket. It takes as a parameter an http Server.

const server = app.listen(port, () => {
    console.log(`Listening on port ${port}`);
});

builder.setServer(server);