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

@danidoble/tracerlog

v0.0.2

Published

Track your logs with a simple tracer using console as always

Downloads

2

Readme

TracerLog

Zero dependency library to trace the log in the console.

Trace log for javascript console When you want to trace the log in the console, you can use this library. For example, you can trace the log in the console like this.

import TracerLog from "@danidoble/tracerlog";

const tracer = new TracerLog();
tracer.init();

Or if you want a common JS, you can do it like this.

<script src="tracerlog.js"></script>
<script>
    const tracer = new TracerLog();
    tracer.init();
</script>

So you can use the console of the browser to see the log as always.

console.log("Hello world");

If you want to get the current log, you can do it like this.

tracer.data; // here are an array with the logs.

By default, when the limit was reached, the log will dispatch an event of browser. So you can listen this event to save with your own code.

document.addEventListener("console:save", function (event) {
    // here you can save the log with your own code.
});

But if you want only one file with the log, you can use the property save_file.

tracer.save_file = true;
// when the limit was reached, the log will be saved in the file.

If you want to change the limit of logs before call to save it, you can do it like this. (by default limit is 300)

tracer.limit = 10;

If you want disable the console but preserve trace

tracer.console = false;

If you want save the log when you want, you can do it like this.

tracer.saveNow();

When the page is unloaded, the log will be saved automatically.

window.location.reload();
// before reload the page, the log will be saved.