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

jsmarka

v1.0.3

Published

Javascript Code Performance Benchmarking App

Downloads

26

Readme

JSMarka

NPM version Build Status

JSMarka is a Javascript Code Performance benchmarking app

jsmarka.com

Running a local copy of JSMarka

Requirements

  1. Node.js v8

  2. MongoDB

Install using npm

$ npm install -g jsmarka
$ jsmarka -p 3000

This gets jsmarka server running on port 3000, visit http://localhost:3000/ and start benchmarking. Use jsmarka --help for more useful commands

Setup (Optional)

If you would like to save tests locally, then you should Register a new OAuth GitHub application

Register a new OAuth GitHub application, set the "Callback" url to http://localhost:3000/auth, then get the apps' "Client ID" and "Client Secret".

Note: You should set the GitHub App "Callback" urls' port to whatever you've configured jsmarka to run on. (see below)

Set up jsmarka via CLI

Run:

$ jsmarka --setup

Setup terminal

After the setup, a .env file containing your setup info is created, to view the contents of this file do:

$ jsmarka --list

You can see that the PORT value is the same port used in the GitHub App Callback URL, that's how yours should be set.

Run jsmarka --help to see useful commands.

Development

If you're installing JSMarka for development purpopses then you have to clone this repo and install its dependencies:

$ git clone http://github.com/kodejuice/jsmarka.git
$ cd jsmarka
$ npm install

Contributing to JSMarka

Submit a pull request to master with passing tests (npm test).

Run:

$ npm run dev

before writting code, as it automatically:

  1. Restarts the server on every change
  2. Re-builds the assets (if you make any changes inside client/)

Use npm run build to manually re-build the assets

Testing

JSMarka uses CasperJS which in turn requires PhantomJS for end-to-end testing, So you should have both casperjs and phantomjs installed on your system.

First, have a separate terminal running npm start

Then run the test suites in another terminal/tab:

$ npm test

Screenshots are taken, find them in the test/screenshots/ folder.