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

cic-webpack-config-factory

v0.0.11

Published

A single webpack configuration for CIC projects

Downloads

6

Readme

CIC Webpack Config Factory

A single webpack configuration for CIC projects

Supported CMS

  • October
  • Wordpress

Install Instructions

  1. yarn add cic-webpack-config-factory
  2. If there is any existing webpack config files, delete them
  3. If there is not any existing webpack config files, create a folder for them
  4. Copy the contents of the samples folder into your now empty webpack config folder
  5. There is at least one change that needs to be made to the config.js template to set it up for your project, so be sure you give it more attention other than a copy-paste.
  6. Add a babel preset to package.json if it is not already there
  "babel": {
    "presets": [
      "react-app"
    ]
  },
  1. Add a browserlist definition to package.json if it is not already there
"browserslist": [
  "defaults"
],
  1. If the project uses a .browserlistrc file, remove it
  2. If the project uses @babel/polyfill replace it with core-js
  3. Update your scripts in package.json if needed to use the new config

Migrating babel polyfill to core-js

Babel polyfill has been deprecated in favor of including core-js. Babel polyfill used core-js under the hood, so the migration process is very straightforward.

import "@babel/polyfill";

becomes

import "core-js/stable";

Sample package.json scripts

"scripts": {
  "dev": "NODE_ENV=development WEBPACK_DEV_SERVER=true webpack-dev-server --config config/webpack/dev.conf.js",
  "watch": "NODE_ENV=development webpack --watch --bail --config config/webpack/prod.conf.js",
  "build": "NODE_ENV=production webpack --bail --config config/webpack/prod.conf.js",
}

Testing Changes

  1. In this project, run yarn link
  2. In an October or Wordpress project, run yarn link cic-webpack-config-factory
  3. Test changes