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

@chiffon/babel-webpack-plugin

v0.0.2

Published

webpack plugin for compiling multiple JavaScript bundles with babel

Downloads

6

Readme

@chiffon/babel-webpack-plugin

Modern browsers can now load ES modules, which means smaller and faster code!

This plugin allows compiling different versions of JavaScript files with Babel, so you can serve older browsers backwards compatable code with your ES modules.

Installation

npm:

npm install --save-dev @chiffon/babel-webpack-plugin

yarn:

yarn add --dev @chiffon/babel-webpack-plugin

Usage

In your webpack config:

const BabelWebpackPlugin = require('@chiffon/babel-webpack-plugin');

module.exports = {
  ...
  module: {
    rules: [
      {
        test: /\.(js|mjs|ts)x?$/,
        use: BabelWebpackPlugin.loader // instead of 'babel-loader'
      },
      ...
    ]
  },
  plugins: [
    new BabelWebpackPlugin({
      targets: [
        {
          target: 'client-legacy',
          excludedPlugins: [],
        },
          target: 'client-modern',
          filename: '[name].[contenthash].mjs',
          chunkFilename: '[name].[contenthash].mjs',
          excludedPlugins: [],
        },
        ...
      ]
    })
    ...
  ]
};

@chiffon/babel-webpack-plugin will pass the value of target to babel, which you can use like so:

In babel.config.js:

function getBabelWebpackPluginTarget(caller) {
  return caller && caller.target
}

module.exports = function(api) {
  const pluginTarget = api.caller(getBabelWebpackPluginTarget)
  const isModernClient = pluginTarget === 'client-modern'
  const isLegacyClient = pluginTarget === 'client-legacy'

  const presetEnvConfig = {
    modules: isModernClient ? false : 'commonjs',
    targets: { node: 'current' },
  }

  // when pluginTarget is specified, we change preset-env's targets to browsers
  if (isModernClient) {
    presetEnvConfig.targets = { esmodules: true }
  } else if (isLegacyClient) {
    presetEnvConfig.targets = '> 0.25%, not dead'
  }

  return {
    presets: [['@babel/preset-env', presetEnvConfig]],
  }
}

Webpack will then build both index.js and index.mjs.

FAQ

What browsers can use ES modules?

All major modern browsers support loading ES modules via the <script type="module> tag. caniuse.com

What benefits are there to ES modules?

Since modern browsers also support features like arrow functions, Map, Set and more, there is no need to polyfill or transform those code. This results in a JavaScript bundle that is smaller and faster to download and parse.

Why compile two or more version?

Older browsers do not understand ES modules, so we still must compile ES5 code in order to provide backwards compatability.

Additionally, you can compile another version for browsers support async/await syntax and get smaller file sizes.

Jason Miller, creator of Preact, explains the various techniques you can apply at https://jasonformat.com/modern-script-loading/.

References and Further Reading