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-preset-futagozaryuu

v3.3.1

Published

Futago-za Ryuu's Babel preset

Downloads

8

Readme

CI npm version dependencies History License

This is a Babel preset of other presets and plugins that I most commonly use.

  • From v2.12, this preset is using the @babel/* dependencies for Babel 7+
  • From v3 this preset is using the proposal plugins directly as Babel 7 dropped the stage presets

installation

$ npm install --save-dev babel-preset-futagozaryuu

usage

Put the following into your .babelrc file:

{
    "presets": [ "futagozaryuu" ]
}

or on the CLI

$ babel src --out-dir lib --presets futagozaryuu

configuration

You can see the complete list of options in babel-preset-futagozaryuu/lib/config/default-options.js.

{
    "presets": [
        [ "futagozaryuu", {

            // set root directory for `babel-plugin-module-resolver`
            "disableResolver": false,
            "root": [ "src" ],

            // disable the use of `@babel/preset-stage-*` plugins
            // (anything not a number between 0 to 3 is the same)
            "stage": 4,

            // Target a spefic version of node
            // (alternative: `package.json#engines.node`)
            "node": 6,

            // Blacklisting the var/const transform
            "exclude": [ "transform-es2015-block-scoping" ],

            // Blacklisting ES Modules transpilation
            "modules": false,

            // re-enable the use of `regenerator`
            "regenerator": true

        } ]
    ]
}

the useBuiltIns option

When using the option useBuiltIns with values usage or entry, ensure that you:

  1. Have the corejs option enabled (by default this is set to { version: 3, proposals: true })
  2. Include the dependencies core-js and regenerator-runtime in your published package

recommendation for vs code users

Adding the following files (and settings) will ensure that VS Code can find your ES6+ files even if you are using babel-plugin-module-resolver to change the root path of your module lookups during transpile.

This is based on a comment in tleunen/babel-plugin-module-resolver#92 by @jgoux.

.vscode/settings.json:

{
    "path-intellisense.mappings": {
        "/": "${workspaceRoot}/src"
    }
}

src/jsconfig.json:

{
    "compilerOptions": {
        "baseUrl": "./",
    }
}

versioning

I have tried to follow semver versioning, but from v2.19 I will follow these rules:

2.18.0 = RELEASE.REVISION.PATCH

  1. RELEASE is incremented each time a new major version of Babel is supported
  2. PATCH is only incremented when
    • a bug is fixed
    • docs are updated between revisions
    • dependency updates between revisions
  3. REVISION is incremented for all other changes
  4. PATCH is reset when REVISION increments

license

Copyright © 2017+ Futago-za Ryuu, https://github.com/futagoza Released under the MIT License, http://opensource.org/licenses/MIT