Closed vaultec81 closed 2 years ago
Have been able to reproduce the issue as well.
Created a PR and you can use this branch to run js-ceramic without the issue until we create a new release.
Thank you for reporting this @vaultec81! I believe the issue should now be addressed. Can you confirm?
Separate note: Seems like @overnight/logger
has been deprecated: https://github.com/seanpmaxwell/overnight#overnightjs
We should make sure to replace this with something different. @ukstv @stephhuynh18 @stbrody
Thank you for reporting this @vaultec81! I believe the issue should now be addressed. Can you confirm?
Yep! Fixed on my end!
Separate note: Seems like
@overnight/logger
has been deprecated: https://github.com/seanpmaxwell/overnight#overnightjsWe should make sure to replace this with something different. @ukstv @stephhuynh18 @stbrody
It has already been replaced with jet-logger by @stephhuynh18 in 2.x
Nice :)
Describe the bug Recently, the maintainer of the
colors
npm package has decided to go rogue. Read me here and here The package@overnightjs/logger
used in Ceramic depends oncolors
To Reproduce
The nodejs code below will demonstrate this issue.
NOTE: you will need to do a fresh install with no package-lock.json or already existing node_modules..
Screenshots After running the above code
And thousands of lines of garbage data being put out.
Ceramic versions As far as I am aware this affects all ceramic versions. Any version that uses
@overnightjs/logger
orcolors
npm package directly or indirectly.I was running Ceramic http client v 1.4.0 but it also happens on latest.
A quick work around is having a package-lock.json, however, new installs will not have this available.