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

@robtucker/webpack-build

v0.0.1

Published

Personal webpack build

Downloads

1

Readme

webpack-build

Personal webpack build.

npm install -D @robtucker/webpack-build

Includes the following environments:

  1. dev
  • ts-loader
  • source-map-loader
  • css modules
  • image-webpack-loader
  • wepack-dev-server
  • hot module replacement
  1. prod
  • concatenate js modules
  • split vendor js in commons chunk
  • minify js
  • extracts and minify styles

Usage

Create webpack config file

Create a webpack config file, webpack.config.js, in your project root and add the following:

const build = require('@robtucker/webpack-build');
const webpackMerge = require('webpack-merge');

const custom = {
    // your custom options go here
    entry: "./src/app.tsx",
}

module.exports = webpackMerge(build.getConfig(), custom)

Create a .env file

You are expected to provide a .env file which will be used at compile time to configure your app. A .env.example file has been provided to demonstrate the format.

At the very beginning of the build process your .env file is loaded and parsed into json by the dotenv package. Webpack then uses the Define Plugin to make this object available inside your project as process.env.CONFIG.

If you are using typescript I highly recommend that you re-export this as a typed object:

export interface ConfigModel {
    API_HOST: string
    APP_VERSION: string
    ENV: string
    GOOGLE_API_KEY: string
    SERVICE: string
    SUPPORT_EMAIL: string
}

export const config: ConfigModel = process.env.CONFIG

Create a Handlebars template

If you are building for web, you must create an html file which represents the entry point of your app.

Webpack uses the html-webpack-plugin which expects to find a handlebars template file, located at src/index.hbs.

The HtmlWebpackPlugin will add a bunch of stuff into your template, such as scripts, stylesheets, favicon, title etc... and then output your file as index.html.

Feel free to copy the demo provided in this repo.