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

@syntro-opensource/webpack-config

v1.4.0

Published

A package to streamline webpack configurations

Downloads

27

Readme

webpack-config

Dependabot npm npm (scoped)

This NPM package provides a common webpack configuration, to be used accross projects built by Syntro GmbH. It serves as a source of truth for configuration and settings.

Directory / Module Sturcture

The configuration in this package is intended to be used for projects, where assets need to be pre-packed and displayed to a web frontend.

In the eyes of this package, every bundle

  • has an entrypoint named bundle.js
  • can contain js, javascript and styles
  • has a separate subfolder in a src/ and dist/ directory

In a Silverstripe module, the structure would look like this:

client/
  ├─ dist/
  │   ├─ bundle_1/
  │   └─ bundle_2/
  │
  └─ src/
      ├─ bundle_1/
      │    ├─ bundle.js
      │    ├─ .eslintrc
      │    ├─ .stylelintrc
      │    ├─ (.babelrc)
      │    └─ (...)
      │
      └─ bundle_2/

For the configuration of eslint and stylelint see the Docs about lint config.

Using the Module Definitions

To set up a webpack build using this module, create a webpack.config.js file in your project root. If we wanted to build the project with the structure described in the previous section, your config should look like this:

const Path = require('path');
const webpackConfig = require('@syntro-opensource/webpack-config');
const {
  resolves,
  modules,
  plugins,
} = webpackConfig;


const ENV = process.env.NODE_ENV;
const PATHS = {
  // The path where your modules are located
  MODULES: 'node_modules',
  // the root path, where your webpack.config.js is located.
  ROOT: Path.resolve(),
  // the root path to your source files
  SRC: Path.resolve('client/src'),
  // thirdparty folder containing copies of packages which wouldn't be available on NPM
  THIRDPARTY: 'thirdparty',
};

const config = [
    {
      name: 'bundle1',
      entry: {
        main: Path.resolve(__dirname, 'client/src/bundle_1')
      },
      output: {
        path: Path.resolve(__dirname, 'client/dist/bundle_1'),
        filename: '[name].js',
      },
      devtool: (ENV !== 'production') ? 'source-map' : '',
      resolve: resolves(ENV, PATHS),
      module: modules(ENV, PATHS),
      plugins: plugins(ENV, PATHS),
    }, {
      name: 'bundle2',
      entry: {
        main: Path.resolve(__dirname, 'client/src/bundle_2')
      },
      output: {
        path: Path.resolve(__dirname, 'client/dist/bundle_2'),
        filename: '[name].js',
      },
      devtool: (ENV !== 'production') ? 'source-map' : '',
      resolve: resolves(ENV, PATHS),
      module: modules(ENV, PATHS),
      plugins: plugins(ENV, PATHS),
    }
];

// do any config manipulation here

module.exports = config;

Finally, add a script to your package.json file:

{
  "scripts": {
    "watch": "webpack --watch --mode development",
    "build": "webpack --mode production",
  }
}

Now, build your bundles using npm run build or npm run watch.

Docs