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

@zero-version/dynamic-webpack.cli

v9.9.14

Published

Create a webpack.config.js file for a CLI or a library with correct bundling and other config.

Downloads

12

Readme

Create a webpack.config.js file for a CLI or a library with correct bundling and other config.

Usage

dynamic-webpack builds a basic webpack config file which automatically bundles any private dependencies, or explicit dependencies (documented in a string array in a bundle.json file).

Usage: dynamic-webpack [options]

Create a webpack.config.js file for a CLI or a library with correct bundling and other config.

Options:
  -V, --version           output the version number
  -d, --projectDir <dir>  The project directory (default: `process.cwd()`)
  -t, --type <type>       type ("cli" or "lib")
  -h, --help              display help for command

Library

This is an example webpack.config.js after running the command dynamic-webpack -t lib:

const path = require('path');
const tsConfigPathsPlugin = require('tsconfig-paths-webpack-plugin');
const includes = require('lodash/includes');
const startsWith = require('lodash/startsWith');

const bundle = [
  // This will be any private dependency, or any dependency explicitly documented in a `bundle.json` file.
];

module.exports = {
  mode: 'production',
  entry: path.resolve(__dirname, 'src', 'index.ts'),
  output: { path: path.resolve(__dirname, 'dist'), filename: 'index.js', libraryTarget: 'commonjs2' },
  module: { rules: [{ test: /.ts$/, exclude: /node_modules/, use: [{ loader: 'ts-loader', options: { transpileOnly: true } }] }] },
  resolve: { plugins: [new tsConfigPathsPlugin()], extensions: ['.mjs', '.js', '.json', '.ts'] },
  target: 'node',
  externals: [
    ({ request }, callback) => {
      const isEntry = path.resolve(request) === path.resolve(__dirname, 'src', 'index.ts');
      const isRelative = startsWith(request, '.');
      const isBundle = includes(bundle, request);
      const isExternal = !isEntry && !isRelative && !isBundle;
      isExternal ? callback(null, 'commonjs ' + request) : callback();
    },
  ],
  stats: 'errors-only',
};

CLI

This is an example webpack.config.js after running the command dynamic-webpack -t cli:

const path = require('path');
const tsConfigPathsPlugin = require('tsconfig-paths-webpack-plugin');
const includes = require('lodash/includes');
const startsWith = require('lodash/startsWith');
const webpack = require('webpack');

const bundle = [
  // This will be any private dependency, or any dependency explicitly documented in a `bundle.json` file.
];

module.exports = {
  mode: 'production',
  entry: path.resolve(__dirname, 'src', 'index.ts'),
  output: { path: path.resolve(__dirname, 'dist'), filename: 'index.js', libraryTarget: 'commonjs2' },
  module: { rules: [{ test: /.ts$/, exclude: /node_modules/, use: [{ loader: 'ts-loader', options: { transpileOnly: true } }] }] },
  resolve: { plugins: [new tsConfigPathsPlugin()], extensions: ['.mjs', '.js', '.json', '.ts'] },
  plugins: [new webpack.BannerPlugin({ banner: '#!/usr/bin/env node', raw: true })],
  target: 'node',
  externals: [
    ({ request }, callback) => {
      const isEntry = path.resolve(request) === path.resolve(__dirname, 'src', 'index.ts');
      const isRelative = startsWith(request, '.');
      const isBundle = includes(bundle, request);
      const isExternal = !isEntry && !isRelative && !isBundle;
      isExternal ? callback(null, 'commonjs ' + request) : callback();
    },
  ],
  stats: 'errors-only',
};

Support ☕

Are you using a package I've developed and finding it useful? Or have you looked at one of my repositories and learnt something new? If so, please consider buying me a coffee. Thanks!