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

babel-blacklist

v1.0.0

Published

Generate a native blacklist for Babel based on Node/io.js version

Downloads

4

Readme

babel-blacklist

Generates a blacklist for features available by default in Node/io.js based on version.

Install with npm install --save-dev babel-blacklist and use it like so (e.g. in a require hook):

require("babel/register")({
  blacklist: require("babel-blacklist")()
})

This makes Babel only transpile what it needs to in your engine.

Documentation

blacklist(version?: string, isStaging?)
blacklist(version: [major, minor, patch], isStaging?)
  • version

    If it's a string, it should be of either the form "vN.N.N" (like "v0.12.0") or "N.N.N" (like "0.12.0"). It is permissible to omit the patch or even the minor, in which it defaults to 0. The 'major' field is required. Note that it doesn't accept shorthands like "v0.12.x" or other npm semver abbreviations. This does not use that syntax.

    If it's an array, it is treated as a 3-tuple [major, minor, patch], where each of them are treated as numbers, coerced if they are not. The major field is required. The rest default to 0.

    This defaults to process.version.

  • isStaging

    If truthy, use the table for io.js' --es-staging flag. Defaults to true if version is not given and --es-staging is set, false otherwise.

Calls to this are memoized.

blacklist.list

Get a list of all the flags for each version. This an object with three keys:

  • defaults - The features not needed by default.
  • staging - The features not needed with --es-staging
  • compareVersion(a, b) - Compare two versions a and b. Returns 1 if greater, 0 if same, and -1 if less.

Both defaults and staging are arrays of objects containing the following properties:

  • version - An object of the form {major, minor, patch}, representing the relative version.
  • blacklist - A list of strings safe for the Babel blacklist option.

Note that this property, defaults, and staging are lazy-loaded for memory reasons.

License

This is licensed under the ISC License.