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

@fwl/logging

v0.1.8

Published

Logging part of Fewlines Web Libraries

Downloads

18

Readme

FWL Logging

Disclaimer: this package is made for our internal usage and is only open source for convenience so we might not consider Pull Requests or Issues. Feel free to fork though.

This is part of the Fewlines Web Libraries packages.

It provides an interface for either a JSON based or a Key/Value based logger.

Both have the same API and does not provide log levels.

This is intended as we consider that a log should either be there or not be there. There should not be differences of level between production and development as we won't be able to use debug logging in production.

Installation

yarn add @fwl/logging

Usage

You first need to create the Logger:

import { createLogger, EncoderTypeEnum } from "@fwl/logging";

const KVLogger = createLogger({
  service: "service-name",
  encoder: EncoderTypeEnum.KV,
});
const JSONLogger = createLogger({
  service: "service-name",
  encoder: EncoderTypeEnum.JSON,
});

After that you make a simple log with the .log function with or without arguments:

KVLogger.log("this is a log");
// service=service-name message="this is a log"

JSONLogger.log("this is a log");
// {"message":"this is a log","service":"service-name"}

KVLogger.log("this is a log", { additionalData: "value" });
// service=service-name additonalData=value message="this is a log"

JSONLogger.log("this is a log", { additionalData: "value" });
// {"additionalData":"value","message":"this is a log","service":"service-name"}

Or you could create a new logger with additional data:

const myProcessLogger = KVLogger.withMeta({ process: "my-process" });
myProcessLogger.log("this is a log");
// service=service-name process=my-process message="this is a log"

const myProcessJSONLogger = JSONLogger.withMeta({ process: "my-process" });
myProcessJSONLogger.log("this is a log");
// {"message":"this is a log","service":"service-name","process":"my-process"}

Logging during tests

If you need to use the logger in a testing environment, we provide an InMemoryLogger class that act as a regular logger, except it will only store the logs. Logs can be accessed using the getLog method, which takes the log index as parameter. The usage is the same, you just need to initialize InMemoryLogger instead of using createLogger().

Here is an example of use in a test file using jest:

import { InMemoryTracer } from "@fwl/tracing";

let logger: InMemoryLogger;

beforeEach(() => {
  logger = new InMemoryLogger();
});

test("verify log entry", () => {
  expect.assertions(1);

  // Call the code that is using a logger.

  const log = logger.getLog(0);

  expect(log).toBe("Your log");
});