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

electrode-ui-logger

v1.1.7

Published

Electrode Logging Utility for UI code

Downloads

3

Readme

Log well and prosper. Happy Logging!

This is a logger for UI code with an Electrode server as backend support.

When your UI code is running on the browser, the logger will save up your logs and send them to the log API {basePath}/api/logger every 10 seconds.

When your UI code is running on the server for SSR, the logger will call request.log. This is why the request option is required on the server.

Install

$ npm install electrode-ui-logger --save

Logger usage

The logging interface provides a simple api for generating developer logs.

import logger from "electrode-ui-logger";

logger.log(tags, data, options);
  • tags - array of strings used to specify log level, transport(s) and to otherwise categorize log entries

  • data - string or object, for transmitting log message and other information

  • options - object with additional options. Currently the only option is request which is required for SSR. For CSR the options are ignored and can be considered optional.

Examples:

logger.log(["error"], {err: "some error occurred"}, {request: req});

logger.log("info", {msg: "hello, world"}); // you can use a string for tags directly 

logger.info({msg: "info is hello world"});

Data objects have some special keys:

  • msg: To include a log message along with other data

    logger.log(["info"], { a: "b", msg: "Log message" });

  • err: Errors should be passed in using the err field:

    logger.log(["error"], { err: err });

Reserved keys (do not use as top-level keys in data): tags

Log levels

  • To set the log level, include it in the tags.
  • Valid log levels: "trace", "debug", "info", "warn", "error", "fatal" (case insensitive)
  • If more than one level is specified, the higher level is used. E.g. logger.log(["info", "warn"], {}) will be logged at warn
  • Level defaults to info if none is specified

API Aliases

These are the API aliases for different log levels:

  • logger.info(data, options)
  • logger.warn(data, options)
  • logger.fatal(data, options)
  • logger.error(data, options)
  • logger.debug(data, options)
  • logger.trace(data, options)