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

traceur-runner

v2.0.1

Published

Runs JavaScript.next code in Node by compiling it with Traceur on the fly, seamlessly

Downloads

6,500

Readme

Run JavaScript.next code in Node, seamlessly

Traceur Runner allows you to run code authored for Traceur seamlessly in Node.js. It does so by compiling the code on the fly using Traceur's mechanism for overriding require, but with some additional smarts.

In particular, Traceur Runner will avoid compiling any dependent packages (i.e. those found in node_modules), unless those packages are marked with "traceur-runner": true in their package.json. This way, you can seamlessly consume most packages without Traceur trying to transpile them, while still getting Traceur compilation for those of your dependencies that are targeted at Traceur themselves.

Additionally, whenever you use Traceur Runner, you will automatically get all error stacks rewritten to have the correct line and column numbers, via the excellent traceur-source-maps package!

Usage

You can use traceur-runner as a binary, pointing it at some code that needs transpiling:

$ traceur-runner my-script.js

You can also use command-line arguments:

$ traceur-runner my-script.js arg1 arg2

If you do this latter, then my-script.js will have a process.argv such that "arg1" is at index 2, "arg2" at index 3, and so on.

Finally, you can also use it programmatically: if you do

require("traceur-runner");

in your source file, any further requires will be transpiled as appropriate.

Traceur Dependency

Traceur Runner peer-depends on Traceur, allowing you to use it with whatever version of Traceur you are already using in your project. This means you should add traceur as a dependency in your package.json, if you haven't already.