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

@rajzik/config-webpack

v6.1.8

Published

Reusable Webpack configs.

Downloads

11

Readme

Webpack Config

Provides Webpack dependencies and configuration. Primarily used in unison with the Lumos CLI.

Extending config

Create file in configs folder:

configs/babel.js

modules.exports = {
  plugins: [new webpack.NamedChunksPlugin()],
};

Settings

Main settings

export interface WebpackOptions {
  analyzeBundle?: boolean;
  buildFolder?: string;
  port?: string | number;
  parallel?: boolean | string | number;
  root?: string;
  react?: boolean;
  sourceMaps?: boolean;
  publicPath?: string;
  srcFolder: string;
  entryPoint?: string;
}

Default values

{
  analyzeBundle = false,
  buildFolder = 'build',
  port = 3000,
  react = false,
  sourceMaps = false,
  srcFolder = 'src',
  publicPath = '/',
  root = process.cwd(),
}

Options

  • analyzeBundle

    • Enable/Disable bundle analyze
  • buildFolder

    • Defines build folder
  • port

    • Defines port
  • react

    • Enable/Disable react usage
  • sourceMaps

    • Enable/Disable source map generation
  • srcFolder

    • Defines source code folder
  • entryPoint

    • Defines file which will be acting as entry point instead of index.html
  • publicPath

    • Defined path where to get scripts
    • useful values: '/', './'
  • parallel

    • Settings for terser plugin
    • fast AF boii
  • aliasPattern

    • Path alias pattern
    • Do not change unless you know what are you doing
    • Example:
    import MyModule from '~/MyModule';
    // this will resolve src/MyModule.[ts,js,tsx,jsx]
    // or src/MyModule/index.[ts,tsx,js,jsx]

CLI Options

  • --sourceMaps
    • Enable source map generation
  • --analyze
    • Enable bundle analyze
  • --parallel / --parallel=<number | string | boolean>
    • Enable/sets parallel configuration
  • --buildFolder=<string>
    • sets build folder
  • --entryPoint=<string>
    • sets entry point for build
    • Entry point is relative to srcFolder

Example:

lumos webpack --entryPoint=appEntry.tsx --sourceMaps --analyze --buildFolder=build

Beemo/webpack