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

@very-amused/slog

v0.5.0

Published

Client to server logging utility.

Downloads

3

Readme

Slog

TS/JS client to server logging. This library is functional, but not actively maintained other than security updates.

Installation

yarn add -D @very-amused/slog

Setup

All configuration for Slog's server is done in slog.config.js in your project directory. This file is expected to be an ES module, with the config as its default export. The config object should be typed using jsdoc as seen below.

// slog.config.js

/** @type {import('@very-amused/slog').ServerOptions}*/
export default {
  certsDir: `${process.env.HOME}/.mycerts/example.tld`
}

Slog's server will only run over HTTPS, and it requires a certificate directory containing a fullchain.pem and privkey.pem file, these files containing a TLS certificate chain and private key respectively. This directory is specified using the certsDir option in slog.config.js.

Usage

  1. Start Slog's server.
yarn slog
  1. Create an Slog client instance in the clientside script you wish to send logs from.
  2. Use the available log, warn, error, or debug methods on the Slog instance to send logs to the server.
import { SlogClient } from '@very-amused/slog'

/* Slog recommends using Typescript, which will validate the format of client URLs at compile time.
No runtime validation is performed at the moment. */
const slog = new SlogClient(`https://example.tld:${SlogClient.DefaultPort}`)

// Any object can be logged (.toString() is used internally), but console CSS is not supported
slog.log('Important info')
slog.error({ message: 'something went wrong', code: 1 })
  1. Logs are displayed on the Slog server console.

Caveats

  1. Unless useColor is set to false in slog.config.js, output will be colorized. A terminal with standard ANSI colors is recommended, output may be difficult to read or understand with custom terminal color themes.