fluent/fluent-logger-node

there is also a NPM library named "fluent-logger-node"

kevinburkenotion opened this issue · 3 comments

"npm info fluent-logger-node" does not turn up this library, which seems bad, given that's the name of the repository.

$ npm info fluent-logger-node

fluent-logger-node@0.0.3 | Proprietary | deps: none | versions: 3
Fluent logger for Node.js

dist
.tarball: https://registry.npmjs.org/fluent-logger-node/-/fluent-logger-node-0.0.3.tgz
.shasum: b06b1817026af23df9458058c5ac84842fb4d2e4

maintainers:
- d_akatsuka <d.akatsuka@gmail.com>

dist-tags:
latest: 0.0.3

published over a year ago by d_akatsuka <d.akatsuka@gmail.com>

$ npm info fluent-logger

fluent-logger@3.3.1 | Apache-2.0 | deps: 1 | versions: 44
fluent-logger implementation for Node.js inspired by [fluent-logger-python].
https://github.com/fluent/fluent-logger-node#readme

keywords: logger, fluent, fluentd

dist
.tarball: https://registry.npmjs.org/fluent-logger/-/fluent-logger-3.3.1.tgz
.shasum: 22b93dbcb995f6106d925357fd266cf76c738c8e
.integrity: sha512-hlLHXS+eJ32dlxEW4xexhjmZKb9/rAPL9suBVRe1uyHGM8QPk+EQe6l4cGlulhILMXTyAXGtFamyzWlHoRqbeQ==
.unpackedSize: 140.9 kB

dependencies:
msgpack-lite: *

maintainers:
- edsiper <edsiper@gmail.com>
- okkez <okkez000@gmail.com>
- repeatedly <repeatedly@gmail.com>
- yssk22 <yssk22@gmail.com>

dist-tags:
latest: 3.3.1

published 4 weeks ago by okkez <okkez000@gmail.com>
okkez commented

https://www.npmjs.com/package/fluent-logger-node is not our project and unmaintained since 7 years ago.
What is the problem?
What should we do?

The problem is people will look at the repository name here and run "npm install fluent-logger-node" and try to install a 7 year old package.

Maybe contact NPM support or the author of the other package, or otherwise make it clear that the package name does not match the repository name.

okkez commented

I see. I will contact the 7 years old package author.

But APIs are different between this library and 7 years old package.
Users who run npm install fluent-logger-node without reading install section of this library can be aware of it when they run their own application.