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

@boldr/tools

v0.1.0-beta.6

Published

Webpack build tools and basic CLI for dev and building universal react applications

Downloads

5

Readme

@boldr/tools

Contains Webpack configuration, and development server.

Usage

Install @boldr/tools and @boldr/cli as dev-dependencies.

Add the following to your package.json:

{
  "dev": "NODE_ENV=development boldr dev",
  "build": "NODE_ENV=production boldr build",
  "clean": "boldr clean",
}

Ensure your project root contains the directory .boldr if not, create it mkdir .boldr. Create another folder called config inside .boldr along with a file called default.js.

mkdir config && touch config/default.js

Copy the configuration at the bottom of this README into default.js.

If you are not using Boldr, you may forgo putting your config directory inside .boldr. Specify CFG_DIR=some/path in your .env file or as an environment variable from your terminal. The directory is resolved based off of the root of your project.

Defined

@boldr/tools will throw an error if process.env.GRAPHQL_ENDPOINT, process.env.API_URL and process.env.API_PREFIX are not set in a .env file (recommended) or added to your runtime command.

The following are inlined at build time via Webpack:

  • __DEV__
  • __SERVER__
  • process.env.GRAPHQL_ENDPOINT
  • process.env.API_URL
  • process.env.API_PREFIX

Vendor Files

There is a section of the default.js where dependencies are added to the development DLLs. Adding files here allows Webpack to place them into the DLLs for development. If you don't care about dev build times, this vendor section isnt that important.

The most important vendor file is located in src/vendor.js. Simply add a dependency to the file by importing it, import 'react';. Whatever is listed in the file is added to a separate chunk for improved caching.

Example Config

Feel free to include something like dotenv in this file and set portions of the config based off of your .env.


// .boldr/config/default.js
// example w/ dotenv
// require('dotenv').config();
// then define say, publicPath as process.env.PUBLIC_PATH
// it will be parsed as a string and passed along.
module.exports = {
  tools: {
    profile: false,
    paths: {
      publicPath: '/static/',
      entry: {
        server: 'src/serverEntry.js',
        client: 'src/clientEntry.js',
      },
      output: {
        server: 'build/server',
        client: 'build/client',
      },
      vendor: 'src/vendor.js',
    },
    // the list of dependencies to include in a DLL bundle for speedier development rebuilds.
    vendor: [
      'react-dom',
      'react-helmet',
      'react-redux',
      'react-router-dom',
      'react',
      'recompact',
      'reselect',
      'redux-form',
      'redux-thunk',
      'redux',
      'serialize-javascript',
      'react-universal-component',
    ],
  },
}