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

babelrc-rollup

v3.0.0

Published

Builds a babel configuration for rollup-plugin-babel by reading .babelrc.

Downloads

38,306

Readme

babelrc-rollup

Builds a babel configuration for rollup-plugin-babel by reading .babelrc.

Install

$ npm install --save-dev babelrc-rollup

Usage

Create a .babelrc file at the root of your project as normal:

{
  "presets": ["es2015"]
}

Inside your rollup.config.js, do this:

import babelrc from 'babelrc-rollup';
import babel from 'rollup-plugin-babel';

export default {
  …
  plugins: [
    babel(babelrc())
  ]
  …
};

Options

path (default: '.babelrc')

If you'd like to customize the path of your babelrc file, pass this option with a string path that can be read using fs.readFile.

config

Use this to avoid reading a babelrc file at all. You could use this to pull the config from package.json instead, for example.

addModuleOptions (default: true)

Disable this option if you do not want the modules: false option to be given to presets in your babel config. You probably don't want to change this unless you're using findRollupPresets.

findRollupPresets (default: false)

Enable this to replace presets with the equivalent rollup-compatible preset, if available. When this option is enabled, babelrc-rollup will try to resolve e.g. es2015-rollup instead of es2015. If no such preset can be found the original will be used.

addExternalHelpersPlugin (default: true)

By default, babelrc-rollup adds the external-helpers plugin, which ensures that only one copy of each helper ends up in your bundle. Disable this option to prevent adding this plugin.

A note on babel versions

Since babel v6.13.0, presets may be given options by using a tuple of [name, opts]. For example, instead of

{
  "presets": ["es2015"]
}

You can do this:

{
  "presets": [
    ["es2015", { "modules": false }]
  ]
}

babelrc-rollup is meant to work with this version of babel or later, but earlier versions are supported by using the right options. The old way to configure the es2015 preset for use with rollup was to use the es2015-rollup preset instead. To continue doing that, call babelrc like so:

babelrc({
  addModuleOptions: false,
  findRollupPresets: true,
  addExternalHelpersPlugin: false
})

If you use the es2015 preset, make sure you install es2015-rollup too. If you can use babel v6.13.0 or later, you should do so.