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

codewars

v0.2.0

Published

CLI for codewars.com

Downloads

11

Readme

codewars

codewars.com library and cli for retrieving, testing locally and attempting katas.

Flow

$ mkdir kata; cd kata

$ codewars next  // or kata_id instead

$ ls
README.md kata.js test.js

$ codewars test  // local testing
Test Passed

$ codewars attempt

Commands

next - retrieves the next kata. Places the stub into kata.js, the test into test.js and the description in the README.md.

<kata_id_or_slug> - same as next, but by providing a specific kata id or slug

test - run the test.js with kata.js

test --watch or -w - will run the test, and watch for changes in the files; re-running the test when a file is updated

Regarding stack-traces

Stack-traces, or at least the line number and the character of the failed code, are visible only in Node v0.11 and above. This is due to the new displayErrors option of the vm module, which is not available on older versions.

A pull-request is welcome for a way to run katas securely and have stack-traces on earlier versions of Node.

License

MIT