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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@wpw/babel-preset-base

v0.0.1

Published

Babel preset for @wps/scripts, without react specific transforms.

Downloads

6

Readme

@wpw/babel-preset-base

This is the default base babel preset to include in non-react projects. It is based on @babel/preset-env and includes some stage-3 plugins.

extends

@babel/preset-env.

You should add .browserslistrc to your project to target your environment. More information can be found here.

If you have incorporated using @wpw/cli, it is already taken care for you.

Plugins

The following babel plugins from stage-3 are included as dependency. They will be loaded by default, but you can disable it through options.

  • @babel/plugin-syntax-dynamic-import
  • @babel/plugin-syntax-import-meta
  • @babel/plugin-proposal-class-properties - with option { "loose": false }.
  • @babel/plugin-proposal-json-strings

Usage

yarn add @wpw/babel-preset-base --dev

In your .babelrc put

{
	"extends": ["@wpw/base"]
}

or in your babel.config.js/babelrc.js

module.exports = {
	extends: ['@wpw/base'],
};

NOTE: babel.config.js is used for project wide configuration. Please refer to the docs to find out which config formatting to use.

Options

@wpw/babel-preset-base can be configured to select which stage-3 plugins to exclude.

babelrc.js

module.exports = {
	extends: [
		'@wpw/base',
		{
			noDynamicImport: true, // disable @babel/plugin-syntax-dynamic-import
			target: 'not dead, > 0.25%', // browserslist query to pass to @babel/preset-env
		},
	],
};

noDynamicImport

boolean, defaults to false.

Set to true to disable @babel/plugin-syntax-dynamic-import.

noImportMeta

boolean, defaults to false.

Set to true to disable @babel/plugin-syntax-import-meta.

noClassProperties

boolean, defaults to false.

Set to true to disable @babel/plugin-proposal-class-properties.

noJsonStrings

boolean, defaults to false.

Set to true to disable @babel/plugin-proposal-json-strings.

Options for @babel/preset-env

What-ever else you pass to the config, is passed directly to @babel/preset-env. This gives you more control on how to configure the most stable env preset.

Please read the documentation for available options.

In most cases, you just need to put a browser query in your browserslist like

> 0.25%, not dead

and you are good to go.

You can put it under browserslist directive under package.json or in a separate .browserslistrc file.

We recommend .browserslistrc because it is shared across many tools. If you bootstrap your project using @wpw/cli, then it will be created automatically.