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

sqlogs

v1.2.2

Published

Quickly send a copy of your `console.log` messages to a SQLite database that you can easily query

Readme

sqlogs Build Status

Quickly send a copy of your console.log messages to a SQLite database that you can easily query.

$ npm install sqlogs
// Import and overwrite console.log
console.log = require('sqlogs');

// Works as usual but also writes a log entry in sqlite
console.log('Hello, world!');
$ sqlite3 sqlogs.sqlite "SELECT * FROM logs"
1| Hello, world!|2018-12-29T06:09:29.516Z|DEFAULT|INFO|

Why?

Often I find my self writing small shell scripts that perform sequential tasks that might get interrupted unexpectedly. In these situations I want to have logs stored on disk that will allow me to check when and where the script stopped and resume from that point on.

Currently I use text files to which JSON strings are appended. This works fine but when I need to filter and sort data things get complicated.

SQL makes filtering and sorting super easy.

How?

I usually start by writing a bunch of console.log statements while building the script. When I'm done I just install sqlogs and assign it to console.log at the top of the file and that's it.

The module will create a file on the same directory that the script is invoked on. The file is named ./sqlogs.sqlite. A table logs is created and all console.log statements are inserted.

Configuration

You can optionally pass an options object as the last argument to change a few settings. Currently you can set the group, level and add additional columns by setting a meta key to an object. The options object must include a sqlogs key with all options. See usage examples below.

Database schema

$ sqlite3 sqlogs.sqlite ".schema"
CREATE TABLE `logs` (`id` integer NOT NULL PRIMARY KEY, `message` text, `timestamp` text, `group` text, `level` text);

Usage Examples

// This is how I usually use this
console.log = require('sqlogs');

// Just write a simple message
console.log('Hello, world!');

// You can pass an options object
console.log('Message', { sqlogs: { group: 'my-script', level: 'DEBUG' } });

// Items in the meta key if needed
// will create columns in the database
console.log('Message', { sqlogs: { meta: { userId: '123' } } });

// Passing multiple arguments also works
console.log(
  'Uno',
  ['Dos'],
  { three: 'Tres' },
  { sqlogs: { meta: { lang: 'ES' } } }
);

Without overwriting console.log (probably a better idea)

const log = require('sqlogs');

// Just write a simple message
log('Hello, world!');

Custom database file path

If you need to customize the path of the SQLite database file you can do the following.

const { createLogger, createSqliteTransport } = require('sqlogs/advanced');
const log = createLogger(createSqliteTransport({ path: './custom.sqlite' }));