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

grunt-traceur-simple

v0.9.10

Published

Grunt Task for ECMAScript 6 to ECMAScript 5 Transpiling with Traceur

Downloads

23

Readme

grunt-traceur-simple

Grunt task that uses the Google Traceur compiler to transpile source files from ECMAScript 6 to ECMAScript 5 syntax. It supports the passing of arbitrary Traceur options and the use of either the dependent Traceur version or an arbitrary peer-installed Traceur version.

The independence of the Traceur internals (which options are supported) and the independence of the Traceur version is the killer feature of this Grunt plugin -- in contrast to similar Grunt Traceur integration plugins.

Getting Started

This plugin requires Grunt ~0.4.0

If you haven't used Grunt before, be sure to check out the Getting Started guide, as it explains how to create a Gruntfile as well as install and use Grunt plugins. Once you're familiar with that process, you may install this plugin with this command:

npm install grunt-traceur-simple --save-dev

Once the plugin has been installed, it may be enabled inside your Gruntfile with this line of JavaScript:

grunt.loadNpmTasks("grunt-traceur-simple");

Options

  • traceurRuntime: The path to the traceur-runtime.js file of Traceur. It can be usually found in the path bin/traceur-runtime.js of a Traceur distribution. The default is the path to the traceur-runtime.js file of the dependent traceur module. Use path.resolve(path.join(__dirname, "node_modules/traceur/bin/traceur-runtime.js")) if you want to use a peer-installed Traceur.

  • traceurCommand: Either the path to the traceur executable of a Traceur installation or distribution or the path to the src/node/command.js file of a Traceur distribution. The default is the path to the command.js file of the dependent traceur module. Use path.resolve(path.join(__dirname, "node_modules/traceur/src/node/command.js")) if you want to use a peer-installed Traceur.

  • traceurOptions: The additional command-line options passed to the traceur executable. Usually used to enable or disable certain transpiling options. The default is "". Use, e.g., --experimental --source-maps for enabling all experimental transpiling features and generate a source-map file.

  • includeRuntime: Set to true for including the Traceur runtime (see traceurRuntime for the path) into the generated output file. Alternatively install the Twitter Bower component traceur-runtime with bower install traceur-runtime and load its traceur-runtime.js yourself in the application. Dependending of the used ECMAScript 6 funtionality in the code, this runtime is needed or not.

Task Calling

Run this task with the grunt traceur command.

Task targets, files and options may be specified according to the Grunt Configuring tasks guide.

Usage Example

Assuming we have the following build environment:

  • Gruntfile.js:
// [...]
grunt.initConfig({
    traceur: {
        options: {
            includeRuntime: true,
            traceurOptions: "--experimental --source-maps"
        },
        "app": {
            files: {
                "out/app.js": [ "src/**/*.js" ]
            }
        }
    }
});
grunt.registerTask("default", [ "traceur" ]);
// [...]

Then running grunt traceur is functionality-wise somewhat equivalent to running traceur --experimental --source-maps --out out/app.js src/*.js.