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

rampant

v0.0.2

Published

Easy profiling on Mac OS X using Google Chrome Canary's frontend.

Downloads

4

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

reidreid

Keywords

Readme

Rampant

Rampant launches your Node.js application into a profiler session using node-webkit-agent paired with the Developer Tools frontend inside Google Chrome Canary.

Caveats

  1. Requires Mac OS X.
  2. Requires Google Chrome Canary.
  3. Does not work if your app depends on STDIN.

Install

npm install rampant

Usage

./node_modules/.bin/rampant /path/to/your/file.js [arguments]

Note: You must provide a fully-qualified path for your script to workaround my shortcomings of path handling. Here's how I workaround this problem in Yeti.

Disclaimer

Rampant depends on bleeding edge Google Chrome to work correctly with node-webkit-agent and Node.js. If you expect this software to work flawlessly, you've chosen the wrong software.

As of the time of this writing, using Rampant is a lot easier than using node-webkit-agent by hand.

If you need a debugger, check out node-inspector because node-webkit-agent does not implement the debugger protocol.

License

BSD. See LICENSE file.

Author

Reid Burke, Yahoo! Inc.