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

recordo

v0.0.6

Published

record browser events for QA to help make tickets/issues

Downloads

2

Readme

Why?

Creating useful bug reports should be dead-simple.

Normal people don't open a debugging console when testing. They just "do stuff and then it breaks". This records the stuff they did and what they said/got from the server to help when filing bugs. It does everything except push the Report an Issue button for them.

Demo it in action here (note the little [[##]] in the bottom-right)

How?

  1. Add ?collect=true to the end of any URL to start collecting a replay log.
  2. (...do stuff until you find a bug...)
  3. Click the Copy button in the bottom-right corner of the page to copy the log (plus your browser info) to your clipboard.
  4. Create a ticket in your issue tracker and paste the log

image

Control Panel

When you hover over the [[23]] (number of messages recorded), the control panel opens up:

image

What are the buttons for?

  • X Stop all the logging and instrumentation
  • Clear clear the log (if you are starting a new test)
  • Copy copy the log and :sparkles: Browser Info :sparkles: to the clipboard (and eventually the exact manifest/config of the server)

For Developer Folks

Something like the following will then be on your clipboard which you can paste into the ticket tracker of your choice (it also contains the request/response JSON with the server):

current_url: 'http://philschatz.com/gh-board/'
current_window: [800, 600],
browser: {os: "MacIntel", userAgent: "Mozilla/5.0..."},
log: [
  ["USER:CLICK", "div.collapse.navbar-collapse"]
  ["XHR:START", "GET", "/api/tasks/226"]
  ["XHR:LOAD",  "GET", "/api/tasks/226", 200, {"id":...}]   // <-- request query and POST body
  ["USER:CLICK", "button.async-button.continue[type='button']>span", "Continue"]
  ["HISTORY:URL", "/courses/3/tasks/226/steps/2/"]   // <-- user going to a different page
  ["XHR:START", "GET", "/api/steps/3653"]
  ["XHR:LOAD", "GET", "/api/steps/3653", 200, "<p>some HTML</p>"] // <-- response HTML
  ["USER:CLICK", "div.answer-letter"]
  ["HISTORY:POP", "/courses/3/tasks/226/steps/1/"]   // <-- clicked browser back button
  ["UNCAUGHT", "data is undefined", "index.js", 1000, 10]  // <-- uncaught JS errors
  ["HISTORY:UNLOAD"]    //  <-- Either refresh was clicked or the user went to another page
  ["WINDOW:SIZE", 800, 600]  //  <-- user resized the window
  ["CONSOLE:LOG", "Some message", 4, [1, true]]
]

Does it work on ??? browser/OS?

Since it's part of the webpage it will. You'll be creating bug reports on mobile devices in no time!

Install

  1. npm install --save recordo
  2. Add the Javascript file
  • For simple sites:
    1. add <script src="node_modules/recordo/dist/recordo.js"></script>
    2. call window.__Recordo.initialize(); __Recordo.start()
  • For browserify projects:
    • add require('recordo').initialize() to the code
    • if you do not want the code in production, wrap it in "production" !== process.env.NODE_ENV and pass that env variable in a way that Uglify can optimize it out
  1. Add the CSS file
  • For LessCSS: add @import (inline) '~recordo/recordo.css';

Development

  1. run npm start
  2. point your browser to http://localhost:8080

TODO:

  • [x] Log all console messages
  • [x] Log window resizes
  • [ ] wrap window.Error because you shouldn't be constructing errors unless you're throwing them