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

watch-it-out

v2.2.2

Published

A way to watch a file or directory for changes and run a command when they occur.

Downloads

20

Readme

Introduction

Are you tired of spreading console.log across your app to debug a cannot read property of undefined: reading foo or something like that?

WatchItOut came to help you with that, and I'll show you how.


Warning

This package does not work without a node environment, it's not meant to be used in the browser.

It uses a events package that is only available in node.


Installation

    npm i watch-it-out
    yarn add watch-it-out

Example of usage

Imagine that you have a object that is a request body from a http request, and you want to know what is happening with it.

    const Watch = require('watch-it-out');

    app.use('/login', (req, res) => {
        const bodyWithTracker = Watch.new(req.body);

        const usecase = new LoginUser();

        usecase.execute(bodyWithTracker);
    });

And inside your usecase you have something like this:

    class LoginUser {
        execute(userInfo) {
            const { email, password } = userInfo; // assessing two properties from the request body

            const user = await User.findOne({ email });

            if (!user) {
                throw new Error('User not found');
            }

            if (user.password !== password) {
                throw new Error('Invalid password');
            }

            return user;
        }
    }

You should see in your console the following logs. So, be careful, because this package will log everything that you do with the object. It means that if you do something like user.password = 'newpassword' it will log it too.

Note: We are working to provide a way to set sensible data to not be logged.

// { action: "acessing property" , property: "email", value: "useremail@gmail" }
// { action: "acessing property" , property: "password", value: "somepassword" }

If you want to config what events log or even provide a context to be logged, you can do it like this:

    const Watch = require('watch-it-out');

    app.use('/login', (req, res) => {
        Watch.config
          .setEvents(['get']) // apply, call
          .setContext({ when: Date.now() });
          .setPrintable(['when']); // Refers to context only
  
        const bodyWithTracker = Watch.new(req.body);

        const usecase = new LoginUser();

        usecase.execute(bodyWithTracker);
    });

And now you should see in your console the following logs:

// { action: "acessing property" , property: "email", value: "useremail@gmail", when: 1590000000000 }
// { action: "acessing property" , property: "password", value: "somepassword", when: 1590000000001 }