
Security News
CVE Volume Surges Past 48,000 in 2025 as WordPress Plugin Ecosystem Drives Growth
CVE disclosures hit a record 48,185 in 2025, driven largely by vulnerabilities in third-party WordPress plugins.
systemjs-plugin-traceur
Advanced tools
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.
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.
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 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.
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.
MIT
FAQs
SystemJS Traceur Plugin ===
We found that systemjs-plugin-traceur demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Security News
CVE disclosures hit a record 48,185 in 2025, driven largely by vulnerabilities in third-party WordPress plugins.

Security News
Socket CEO Feross Aboukhadijeh joins Insecure Agents to discuss CVE remediation and why supply chain attacks require a different security approach.

Security News
Tailwind Labs laid off 75% of its engineering team after revenue dropped 80%, as LLMs redirect traffic away from documentation where developers discover paid products.