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

@sbovyrin/webpack-mini

v1.1.2

Published

Minimal webpack config that is easy extending when it's necessary

Downloads

2

Readme

webpack-mini

NPM npm GitHub issues npm (scoped)

Read Changelog before updating!

Minimal webpack config that is easy extending when it's necessary.

By default:

  • input file index.js must be located in src directory
  • html-template file must be located in project root
  • output files are located in dist directory

Quick start

  1. Create main js file in src directory: /src/index.js
  2. Create index.html template in your project root: /index.html
  3. Create webpack.config.js file in your project root
    • add next code to the file:
      const { defaultConfig } = require('@sbovyrin/webpack-mini');
            
      module.exports = defaultConfig();
  4. Optionally install webpack-dev-server: npm i --save-dev webpack-dev-server
  5. Start development server: npx webpack --watch --env.dev
    • or: npx webpack-dev-server --env.dev
  6. Build the project for production: npx webpack --env.prod
    • output files are located in /dist directory

Features

  • Ready to work out of the box
  • Easy to customize
  • Output separate files
    • app.js (your application)
    • vendor.js (app's dependencies)
    • runtime.js (wepback runtime)
    • styles.css (app's CSS)
  • Production files are optimized (including tree-shaking)
  • Hot server reload for development
  • Lightweight and low resource consumer

Customize

Change entry configuration

  • Create webpack.config.js file
    const { defaultConfig } = require('@sbovyrin/webpack-mini');
    
    module.exports = defaultConfig();
  • Create your customized config function
    // here 'env' has value passed to --env (i.e '--env.prod' in script command)
    function customizeConfig(env) {
      return {
        entry: 'mysource/app.js'
      }
    }
    
    module.exports = defaultConfig(customizeConfig);
  • Now your entry point is mysource/app.js

Using React.js

Comming soon...