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

@vleesbrood/webpack-starter-cli

v4.9.0

Published

webpack starter cli tool

Downloads

16

Readme

webpack-starter-cli FOSSA Status CI

npm install -g @vleesbrood/webpack-starter-cli

extensible webpack starter kit cli tool

pre-requisites

  • Node & NPM

usage

# start a hot-reloading server
$ starter serve

Run a live-reloading server with frontend

Options:
  --help         Show help                                             [boolean]
  -c, --config   pass the configuration path    [default: "./starter.config.js"]
  -m, --mode     specify the compilation mode           [default: "development"]
  -p, --port     specify the port                                [default: 9000]
  -h, --host     specify the host                         [default: "127.0.0.1"]
  -v, --version  Show version number                                   [boolean]

# build the project
$ starter build

Build the application

Options:
  --help         Show help                                             [boolean]
  -c, --config   pass the configuration path    [default: "./starter.config.js"]
  -w, --watch    watch source and compile on changes            [default: false]
  -v, --version  Show version number                                   [boolean]

features

extend the configuration

Use .babelrc to add babel presets!

{
  "presets": [
    "@babel/preset-react"
  ]
}

Add in custom webpack configuration using starter.config.js:

const path = require('path');
const SRC = './src';

const webpack = {
  entry: 'index.jsx',

  resolve: {
      assets: path.join(__dirname, SRC, 'assets'),
      components: path.join(__dirname, SRC, 'components'),
      src: path.join(__dirname, SRC),
      state: path.join(__dirname, SRC, 'state'),
      views: path.join(__dirname, SRC, 'views')
  }
};

module.exports = () => {
  return {
    webpack
  };
}

The custom configuration will be merged together with the default configuration.

gotcha's

The cli assumes a folder layout like this:

 |- src/
 |- package.json
 |- .babelrc
 |- starter.config.json

If you installed the cli globally, you have to add @babel/core to your package.json if you want to customize the babel-loader.

# installing @babel/core is required if you need a custom preset
$ npm install --save @babel/core @babel/preset-react
{
  "presets": [ "@babel/preset-react" ]
}