Provide steps for shrinkwrap users to fix their builds after 2.2.0 was unpublished about ansi-styles

[desbo]

If it's any help you can use https://gist.github.com/desbo/906326b08c05aa09e2fe to replace any occurrences of ansi-styles at 2.2.0 with 2.2.1 in npm-shrinkwrap.json.

[dr-nafanya]

Manual search/replace of [email protected] to [email protected] in npm-shrinkwrap.json does work.

[Qix-]

@xcatliu We're aware of the problems with unpublish 👍 Checkout the post mortem.

[Qix-]

Without knowing anything about npm-shrinkwrap, I would imagine manually adjusting the version to 2.2.1 would be the ideal method.

Would love to have a definitive answer.

// @sindresorhus

[Qix-]

Thank you @dr-nafanya.

[Qix-]

Keeping open for discovery.

[tlrobinson]

Yes, manually editing works in this case, however it leaves the color-convert dependency that was added in 2.2.0 in npm-shrinkwrap.json, which I think is harmless (aside from a little bit of wasted bandwidth), but if a dependency were added rather than removed this probably wouldn't work.

[Qix-]

It shouldn't be a problem. The new version of color-convert was designed to work with the existing chalk API.

If it becomes a problem, let me know.

Good catch though 👍

[xcatliu]

Thanks @dr-nafanya
Problem fixed when I manually replaced [email protected] to [email protected] in npm-shrinkwarp.json

ansi-styles is an awesome module to control styles in terminal, but please known It is generally considered bad behavior to remove versions of a library that others are depending on! Consider using the deprecate command instead, if your intent is to encourage users to upgrade.

Anyway, many thanks to @Qix- for the awesome library!