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

quickscope-cli

v0.2.0

Published

Cli client for quickscope

Downloads

10

Readme

Faster tests and quicker feedback cycles save lives!

What?

Quickscope-cli is a test runner invoker (quite a mouthful!). It sole purpose in life is to help you with running only the tests that you need.

The problem

The main problem we are solving here is how normal node projects are built. A standard workflow for node module looks something like this:

  • You have your amazing build system (gulp, grunt, broccoli, etc...)
  • Build system watches the file system.
  • If some file changes then it will trigger the test command that will invoke your favourite test runner.
  • Tests will run and you will most likely are happy with the result.

This looks good on the paper, but it just wont scale. Running all the tests with each save is a huge overhead.
It will work fine if you have a small amount of tests, but what if you have thousands of test cases? Even if the tests are well written executing them will take time.

The solution

Instead of watching all the files and triggering all the tests when any of them changes lets just watch all the tests files and trigger relevant tests when any of those files change? Simple eh!?

This will create much faster feedback loops, will reduce the noise and give you better overall developing flow.

Getting started

  $ npm install quickscope-cli -g
  $ quickscope
Params
  • -c - configuration file. json or js
Configurations

Quickscope will either use configurations from your package.json file or from any file that you pass with -c param.

package.json
"config": {
  "quickscope": {
    "files": "lib/__tests__/**.js",
    "cmd": "jest"
  }
}
custom config file
{
  "files": "lib/__tests__/**.js",
  "cmd": "jest"
}

Testing

npm test

License

MIT