</>PackageGraphPackageGraph

abstract-logging

npmv2.0.1

A noop logger that conforms to the Log4j interface for modules to stub out internal logging

Not recommended for new projects

No — abstract-logging should not be adopted for new projects. Last published 2153 days ago.

  • ?Adoption: grade ?, Not reported by this registry.

    No download data reported for this package yet.

  • FMaintenance: grade F, Failing.

    Last published 2153 days ago.

  • AWeight: grade A, Excellent.

    Zero runtime dependencies, about 2.2 KB installed.

  • BSupply chain: grade B, Good.

    This package has a single maintainer (bus factor of 1).

  • ALicense: grade A, Excellent.

    MIT — permissive, with no copyleft found in the dependency tree.

Grades are computed deterministically from registry metadata collected by PackageGraph — downloads, dependents, publish dates, the resolved dependency tree, maintainer count, and declared licenses. No third-party scores are used.

Install cost

What you actually take on by adding abstract-logging to a project.

0
Direct dependencies

Runtime packages this one declares itself.

0
Total installed

Distinct packages in the full runtime tree, deduplicated the way a package manager would.

2.2 KB
Install size

Unpacked size of this package plus its entire runtime tree.

—
Tree depth

Longest resolved dependency chain below this package.

Compatibility

Node.js
No constraint declared
Module format
CommonJS only
TypeScript
No bundled types
Install scripts
None

Quick start

A usage example from the abstract-logging README.

jsFull README ↗
'use strict'

function AwesomeLibrary (options) {
  this.log = (options.logger) ? options.logger : require('abstract-logging')
}

AwesomeLibrary.prototype.coolMethod = function () {
  this.log.trace('AwesomeLibrary.coolMethod was invoked')
  return {}
}

module.exports = AwesomeLibrary

abstract-logging vs the alternatives

Packages solving a similar problem in the npm ecosystem, compared on the signals that drive an adoption decision.

PackageWeekly downloadsDependentsLicenseLast release
abstract-loggingthis page01MIT5 years ago
loglevel02MIT1 day ago
loglevel-plugin-prefix01MIT1 day ago
@open-draft/logger01MIT1 day ago
log-symbols01MIT1 day ago
logkitty01MIT1 day ago

Used by

Popular packages that depend on abstract-logging.

fastifynpm

Fast and low overhead web framework, for Node.js

↓ 8.9M/wk◈ 4 dependents⚖ MITTS

Relationship graph

Dependencies (left) and dependents (right) of abstract-logging.

fastifyabstract-logging
abstract-logging dependencies dependents

Frequently installed together

undicinpm

An HTTP/1.1 client, written from scratch for Node.js

↓ 158.5M/wk◈ 15 dependents⚖ MITTS
http-errorsnpm

Create HTTP error objects

↓ 149.4M/wk◈ 7 dependents⚖ MIT
eslintnpm

An AST-based pattern checker for JavaScript.

↓ 138.4M/wk◈ 279 dependents⚖ MITTS
varynpm

Manipulate the HTTP Vary header

↓ 100.2M/wk◈ 4 dependents⚖ MIT
rfdcnpm

Really Fast Deep Clone

↓ 46.8M/wk◈ 3 dependents⚖ MITTS
process-warningnpm

A small utility for creating warnings and emitting them.

↓ 0/wk◈ 2 dependents⚖ MITTS
@fastify/fast-json-stringify-compilernpm

Build and manage the fast-json-stringify instances for the fastify framework

↓ 0/wk◈ 1 dependents⚖ MITTS
light-my-requestnpm

Fake HTTP injection library

↓ 0/wk◈ 1 dependents⚖ BSD-3-ClauseTS
toad-cachenpm

LRU and FIFO caches for Client or Server

↓ 0/wk◈ 1 dependents⚖ MITTS
@fastify/ajv-compilernpm

Build and manage the AJV instances for the fastify framework

↓ 0/wk◈ 2 dependents⚖ MITTS
@fastify/errornpm

A small utility, used by Fastify itself, for generating consistent error objects across your codebase and plugins.

↓ 0/wk◈ 2 dependents⚖ MITTS
@fastify/proxy-addrnpm

Determine the address of a proxied request

↓ 0/wk◈ 1 dependents⚖ MITTS

Release history

No releases in the last two years, typically about 1119 days apart.

Recent versions of abstract-logging
VersionPublishedSizeLicense
2.0.1latest5 years ago2.2 KBMIT
2.0.06 years ago1.9 KBMIT
1.0.010 years ago—MIT

Overview

abstract-logging is an npm package that a noop logger that conforms to the Log4j interface for modules to stub out internal logging. It has 1 known dependents in the graph. The latest version is 2.0.1, released under the MIT license.

Who should use it

Teams working in the npm ecosystem who need a noop logger that conforms to the Log4j interface for modules to stub out internal logging and value a focused solution.

When not to use it

Consider an alternative if you need to have first-class TypeScript types out of the box, or if a more actively-maintained option better fits your npm stack.

Pros

  • Clear open-source license (MIT).
  • Zero runtime dependencies — minimal footprint.

Cons

  • No bundled TypeScript types (may require a separate @types package).

Auto-generated from collected registry metadata. No external claims are inferred.

Maintainers

jsumners

Keywords

logloggerloggingpino

Frequently asked questions

Should I use abstract-logging?

No — abstract-logging should not be adopted for new projects. Last published 2153 days ago.

How do I install abstract-logging?

Run `npm install abstract-logging` to add abstract-logging to your npm project.

What license is abstract-logging released under?

abstract-logging is distributed under the MIT license.

How popular is abstract-logging?

npm does not publish download counts. Within PackageGraph's crawl, 1 known packages depend on abstract-logging.

Is abstract-logging still maintained?

The most recent release of abstract-logging (v2.0.1) was published 5 years ago.

Does abstract-logging run install scripts?

No. abstract-logging does not define preinstall, install, or postinstall scripts, so installing it does not execute publisher-supplied code.