@jsenv/logger - npm Package Compare versions

Comparing version 4.0.1 to 4.1.0

package.json

 {
   "name": "@jsenv/logger",
-  "version": "4.0.1",
+  "version": "4.1.0",
   "description": "Control verbosity of logs during a function execution.",
@@ -5,0 +5,0 @@ "license": "MIT",

readme.md

@@ -5,19 +5,4 @@ # logger
 
-[![github package](https://img.shields.io/github/package-json/v/jsenv/jsenv-logger.svg?logo=github&label=package)](https://github.com/jsenv/jsenv-logger/packages)
 [![npm package](https://img.shields.io/npm/v/@jsenv/logger.svg?logo=npm&label=package)](https://www.npmjs.com/package/@jsenv/logger)
-[![github ci](https://github.com/jsenv/jsenv-logger/workflows/ci/badge.svg)](https://github.com/jsenv/jsenv-logger/actions?workflow=ci)
-[![codecov coverage](https://codecov.io/gh/jsenv/jsenv-logger/branch/master/graph/badge.svg)](https://codecov.io/gh/jsenv/jsenv-logger)
 
-# Table of contents
-
-- [Presentation](#Presentation)
-- [Installation](#installation)
-- [Documentation](#usage)
-  - [createLogger](#createLogger)
-  - [logLevel](#logLevel)
-  - [logger](#logger)
-  - [Migration from console](#migration-from-console)
-
-# Presentation
-
 You want to use `@jsenv/logger` when you have many logs with different purposes and controls which type of logs are actually written.
@@ -30,3 +15,3 @@
 ```console
-npm install @jsenv/logger@3.3.1
+npm install @jsenv/logger
 ```
@@ -33,0 +18,0 @@

src/createLogger.js

@@ -66,15 +66,15 @@ import {
 
-const debug = console.debug
+const debug = (...args) => console.debug(...args)
 
 const debugDisabled = () => {}
 
-const info = console.info
+const info = (...args) => console.info(...args)
 
 const infoDisabled = () => {}
 
-const warn = console.warn
+const warn = (...args) => console.warn(...args)
 
 const warnDisabled = () => {}
 
-const error = console.error
+const error = (...args) => console.error(...args)
 
@@ -81,0 +81,0 @@ const errorDisabled = () => {}

New alerts

License Policy Violation

License

This package is not allowed per your license policy. Review the package's license to ensure compliance.

Found 1 instance in 1 package

New author

Supply chain risk

A new npm collaborator published a version of the package for the first time. New collaborators are usually benign additions to a project, but do indicate a change to the security surface area of a package.

Found 1 instance in 1 package

Fixed alerts

License Policy Violation

License

This package is not allowed per your license policy. Review the package's license to ensure compliance.

Found 1 instance in 1 package

Major refactor

Supply chain risk

Package has recently undergone a major refactor. It may be unstable or indicate significant internal changes. Use caution when updating to versions that include significant changes.

Found 1 instance in 1 package

Worsened metrics

Total package byte prevSize

18312

decreased by-2.63%

Number of lines in readme file

99

decreased by-13.16%

No dependency changes