Closed micalevisk closed 2 years ago
@micalevisk Could you please send a PR for that?
the version used here is 0.6.2
. Do you think upgrading it to the latest working major will be fine? I didn't manage to run the tests here.
@micalevisk Depends on what Node version they support. What were the breaking changes for 1.0.0?
well that will be hard to tell as there's no changelog to look at https://github.com/Marak/colors.js/compare/v0.6.2...v1.0.0
Keeping the current semver range won't cover the latest version of colors
.
I didn't really get how colors
is being used by forever
tbh. I've just found this one https://github.com/foreversd/forever/blob/2211e32a288b97c3c3d1e27f41370a9a489ee833/lib/forever/cli.js#L629
Probably we need to replace it with colorette :)
Hi, I think the problem is on prettyjson module. It uses the colors.js version 1.4.2. Anyway on how to fix it?
oh, yeah
I guess we only need to wait them https://github.com/rafeca/prettyjson/pull/54
Forever crashing is causing many apps & servers to be offline right now. It'd be great if we could switch to a prettyJson fork temporarily if that PR can't make it shortly.
rm -rf /usr/lib/node_modules/forever/node_modules/prettyjson/node_modules/colors/
cd /usr/lib/node_modules/forever/node_modules/prettyjson
npm install colors@1.4.0
You can do this as an temporary solution before prettyjson
apply rafeca/prettyjson#54.
Had some servers using npx forever
in built environments that were particularly complex to patch.
there is a fixed version of prettyjson coming up, will release new forever when that happens
Fix released in 4.0.2
Fix released in 4.0.2
Thank you
Thanks everyone for that patch!
https://github.com/foreversd/forever/blob/2211e32a288b97c3c3d1e27f41370a9a489ee833/package.json#L24
colors
was intentionally compromised by the author. The latest working version is1.4.0
. So I believe you need to pin that version to1.4.0
to prevent issues from the next upgrades.