loglevel-plugin-prefix

npmv0.8.4TypeScript

Plugin for loglevel message prefixing

Not recommended for new projects

No — loglevel-plugin-prefix should not be adopted for new projects. Last published 3006 days ago.

?Adoption: grade ?, Not reported by this registry.
No download data reported for this package yet.
FMaintenance: grade F, Failing.
Last published 3006 days ago.
AWeight: grade A, Excellent.
Zero runtime dependencies, about 62 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 loglevel-plugin-prefix to a project.

Direct dependencies

Runtime packages this one declares itself.

Total installed

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

62 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: Types included
Install scripts: None

Quick start

A usage example from the loglevel-plugin-prefix README.

javascriptFull README ↗

var defaults = {
  template: '[%t] %l:',
  levelFormatter: function (level) {
    return level.toUpperCase();
  },
  nameFormatter: function (name) {
    return name || 'root';
  },
  timestampFormatter: function (date) {
    return date.toTimeString().replace(/.*(\d{2}:\d{2}:\d{2}).*/, '$1');
  },
  format: undefined
};

loglevel-plugin-prefix vs the alternatives

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

Package	Weekly downloads	Dependents	License	Last release
loglevel-plugin-prefixthis page	0	1	MIT	8 years ago
loglevel	0	2	MIT	1 day ago
@open-draft/logger	0	1	MIT	1 day ago
abstract-logging	0	1	MIT	1 day ago
axios	106.5M	4	MIT	1 day ago
cross-fetch	32.9M	2	MIT	1 day ago

Dependencies

Declared by loglevel-plugin-prefix v0.8.4. Runtime dependencies are installed with the package; dev dependencies are not.

Dev (11)

chai ^4.1.2chalk ^2.4.1eslint ^3.19.0eslint-config-airbnb-base ^11.3.2eslint-plugin-chai-friendly ^0.3.6eslint-plugin-import ^2.12.0loglevel ^1.6.1loglevel-plugin-mock ^0.1.0mocha ^3.5.3sinon ^2.4.1uglify-js ^3.4.0

Used by

Popular packages that depend on loglevel-plugin-prefix.

@wdio/loggernpm

A helper utility for logging of WebdriverIO packages

↓ 0/wk◈ 6 dependents⚖ MITTS

Relationship graph

Dependencies (left) and dependents (right) of loglevel-plugin-prefix.

loglevel-plugin-prefix dependencies dependents

Frequently installed together

safe-regex2npm

detect possibly catastrophic, exponential-time regular expressions

↓ 0/wk◈ 2 dependents⚖ MITTS

loglevelnpm

Minimal lightweight logging for JavaScript, adding reliable log level methods to any available console.log methods

↓ 0/wk◈ 2 dependents⚖ MITTS

Release history

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

Recent versions of loglevel-plugin-prefix
Version	Published	Size	License
0.8.4latest	8 years ago	62 KB	MIT
0.8.3	8 years ago	—	MIT
0.8.2	8 years ago	—	MIT
0.8.1	8 years ago	—	MIT
0.8.0	8 years ago	—	MIT
0.7.2	8 years ago	—	MIT
0.7.1	8 years ago	—	MIT
0.7.0	8 years ago	—	MIT
0.6.0	8 years ago	—	MIT
0.5.3	9 years ago	—	MIT
0.5.2	9 years ago	—	MIT
0.5.1	9 years ago	—	MIT
0.5.0	9 years ago	—	MIT
0.4.2	9 years ago	—	MIT
0.4.1	9 years ago	—	MIT

Overview

loglevel-plugin-prefix is an npm package that plugin for loglevel message prefixing. It has 1 known dependents in the graph. The latest version is 0.8.4, released under the MIT license.

Who should use it

Teams working in the npm ecosystem who need plugin for loglevel message prefixing and value a focused solution.

When not to use it

Consider an alternative if you need to or if a more actively-maintained option better fits your npm stack.

Pros

Ships TypeScript type definitions.
Clear open-source license (MIT).

Cons

No significant drawbacks detected from available metadata.

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

Maintainers

kutuluk

Keywords

browser colored log logger logging loglevel node plugin prefix

Frequently asked questions

Should I use loglevel-plugin-prefix?

No — loglevel-plugin-prefix should not be adopted for new projects. Last published 3006 days ago.

How do I install loglevel-plugin-prefix?

Run `npm install loglevel-plugin-prefix` to add loglevel-plugin-prefix to your npm project.

What license is loglevel-plugin-prefix released under?

loglevel-plugin-prefix is distributed under the MIT license.

How popular is loglevel-plugin-prefix?

npm does not publish download counts. Within PackageGraph's crawl, 1 known packages depend on loglevel-plugin-prefix.

Is loglevel-plugin-prefix still maintained?

The most recent release of loglevel-plugin-prefix (v0.8.4) was published 8 years ago.

Does loglevel-plugin-prefix run install scripts?

No. loglevel-plugin-prefix does not define preinstall, install, or postinstall scripts, so installing it does not execute publisher-supplied code.