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

@emmiep/babel-plugin-strip-parcel-hmr

v2.0.0

Published

An experimental Babel plugin for removing [hot module replacement] (HMR) code from production bundles created with [Parcel].

Downloads

5

Readme

babel-plugin-strip-parcel-hmr

An experimental Babel plugin for removing hot module replacement (HMR) code from production bundles created with Parcel.

Currently the following syntaxes are supported:

  • Tests in if and else statements
  • Tests in the ternary ?: operator
  • Checking for HMR with module.hot and module['hot']
  • Checking for HMR with typeof module.hot
  • Checking for HMR with 'hot' in module
  • Negating tests with !

Examples

In

if (module.hot) {
  module.hot.accept(() => {
    // update module
  });
}

const value = module.hot ? 'in development' : 'in production';

// rest of the code here

Out

const value = 'in production';

// rest of the code here

In

if (!module.hot) {
  // only when HMR is disabled
}

Out

{
  // only when HMR is disabled
}

Installation

npm install @emmiep/babel-plugin-strip-parcel-hmr

Usage

.babelrc

{
  "env": {
    "production": {
      "plugins": [
        "@emmiep/babel-plugin-strip-parcel-hmr"
      ]
    }
  }
}

The plugin would normally only be used for the production environment (which is automatically set when running parcel build) to preserve the HMR code during development. This is accomplished by using the env option in .babelrc as shown above.

Options

objectName

string, defaults to module.

The name of the global object containing a property (propertyName) used when checking if HMR is enabled.

propertyName

string, defaults to hot.

The name of the property used when checking if HMR is enabled.

Caveats

Currently Parcel is not implementing tree-shaking, which means functions only used during development for HMR will still be included in the production bundles unless they're defined inside if statements testing for HMR. For instance any module imported using the ES6 import keyword will always be included in the production bundle.