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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@live2ride/dblog

v1.4.0

Published

simple logging to mssql database

Readme

MS SQL Server Logging Library

Easily log events to a Microsoft SQL Server (MSSQL) database using JavaScript.

Table of Contents

Configuration

Setup

Create all necessary tables and functions in the database.

import {dbLogSetup} from "@live2ride/dbLog";
dbLogSetup();

Direct Configuration

Configure the database connection using environment variables and initialize the logging library.

import DB from "@live2ride/db";
import DBLog from "@live2ride/dbLog";

// Database configuration
const dbConfig = {
  database: process.env.DB_DATABASE,
  user: process.env.DB_USER,
  password: process.env.DB_PASSWORD,
  server: process.env.DB_SERVER,
};

// Initialize database and logger
const db = new DB(dbConfig);
const dbLog = new DBLog(db);

Usage

Logging Events

Start a log, update it with messages, and finalize with a status.

// Start log
dbLog.start({
  title: "Some Cleanup Process",
  message: "Cleanup started",
  props: {
    dir: "/xyz",
    options: {
      more: "Additional options",
    },
  },
});

// Update log with progress
dbLog.update("Cleaning directory xyz");
dbLog.update("Finished cleaning xyz/abc");
dbLog.update("Finished cleaning xyz/def");

// Finalize log with status
dbLog.success("Cleanup finished");
// or
dbLog.warning("Missed a few files");
// or
dbLog.error(new Error("Some error occurred"));

Examples

Fetching Logs

Retrieve all logs from the database.

const logs = await db.exec('SELECT * FROM dbo.log');
console.log(logs);

/*
Example Output:
[
  {
    logid: ********,
    status: 'success',
    title: 'dbLogger',
    msg: 'Finished',
    start_time: ********,
    end_time: ********,
    props: { obj: 'Some additional props' },
    error: undefined,
    heartbeat: ********,
    run_time: 1
  }
]
*/
await dbLog.get.recent()
await dbLog.get.log(logid) /* with additional column **messages** an array of logDetails messages  */
await dbLog.get.errors()
await dbLog.get.warnings()

Database Schema

Log Table Fields

  • logid: Identity column.

  • status: success, warning, error.

  • title: Title identifying your process.

  • msg: Additional messages (all messages are saved in logDetails).

  • start_time: Time the process started.

  • end_time: Time the process ended.

  • props: Any object you want to save for troubleshooting, such as parameters.

  • error: Field to hold your error object for easier troubleshooting.

  • heartbeat: Indicates that dbLog is alive by checking in every few seconds.

  • run_time: Duration the process has been running in seconds.