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

systemjs-plugin-traceur

v0.0.3

Published

SystemJS Traceur Plugin ===

Downloads

1,580

Readme

SystemJS Traceur Plugin

Provides Traceur transpilation in the browser and in builds when using SystemJS 0.19.12+ and SystemJS Builder 0.15+.

Compatible with the the automatic Rollup optimizations in SystemJS Builder.

Usage

jspm

jspm install plugin-traceur

Then set transpiler: 'plugin-traceur' in the jspm.js config file.

Alternatively use jspm init -p to set up the plugin automatically.

SystemJS

As well as this plugin, Traceur and Traceur Runtime must be manually configured.

This plugin is available at npm install systemjs-plugin-traceur.

Traceur can be installed via npm install traceur or from GitHub at https://github.com/jmcriffey/bower-traceur and https://github.com/jmcriffey/bower-traceur-runtime.

The npm version contains traceur.js and traceur-runtime.js within the bin folder.

The plugin can be used in SystemJS with the following configuration:

SystemJS.config({
  map: {
    'plugin-traceur': 'path/to/systemjs-plugin-traceur/plugin-traceur.js',
    'traceur': 'path/to/traceur.js',
    'traceur-runtime': 'path/to/traceur-runtime.js'
  },
  meta: {
    'traceur': {
      format: 'global',
      exports: 'traceur'
    },
    'traceur-runtime': {
      format: 'global',
      exports: '$traceurRuntime'
    }
  },
  transpiler: 'plugin-traceur',
  transpilerRuntime: false
});

It is important to set the transpilerRuntime: false option so that Traceur doesn't interfere with the deprecated internal Traceur compilation layer of SystemJS.

The metadata above is necessary otherwise Traceur will not load property in SystemJS.

The plugin can also be configured as a loader through metadata in SystemJS.

Traceur Options

Traceur compilation options can be set via traceurOptions in SystemJS:

SystemJS.config({
  traceurOptions: {
    asyncFunctions: true
  }
});

The full list of configuration options can be found at https://github.com/google/traceur-compiler/blob/master/src/Options.js#L25.

Building and Bundling

Build support works with no further configuration through the standard jspm build and bundle commands.

To build with SystemJS builder, use the following build configuration:

builder.bundle('app.js', 'out-bundle.js'); // create a named bundle
builder.buildStatic('app.js', 'out-static.js', { format: 'cjs' }); // create a static optimized build

When using builder.buildStatic, the ES module structure will be preserved and Rollup optimizations will included automatically allowing for static dead code removal.

Because Traceur runtime is a global, it can't be included in the Rollup optimizations. It can be useful to entirely separate out the traceur-runtime dependency from the build and have it in its own bundle, for example via:

builder.buildStatic('app.js - traceur-runtime', 'out-static.js', { format: 'cjs' });

This way, the entire bundle runs through Rollup for a fully-optimized output.

LICENSE

MIT