Daniel Ruf
Daniel Ruf
> the omission of a v3.0.0 release/tag I guess this was just forgotten by @cpojer. Besides this, react, relay, create-react-class and so on are projects which are created and maintained...
boomerang and so on too ;-)
:+1: also see http://stackoverflow.com/questions/2430175/what-is-the-best-jquery-wysiwym-textile-editor
For anyone who is affected, here are ways to check, which packages have to pin the version (the ones which directly use `colors`): for npm: ``` npm ls colors ```...
@Solixity see also https://github.com/Marak/colors.js/issues/285#issuecomment-1008168237
@RPGillespie6 see https://github.com/Marak/colors.js/issues/285#issuecomment-1008168237 @nebulade not really, see https://diff.intrinsic.com/colors/1.4.1/1.4.2. He added another loop to colors/safe, probably because he oversaw this. reference: https://github.com/Marak/colors.js/issues/285#issuecomment-1008357669
@Hamahmi yes, please see https://github.com/Marak/colors.js/issues/285#issuecomment-1008367265
@kevinlonigro see https://github.com/aws/aws-cdk/pull/18324
The .2 release added the same code to colors/safe, see https://diff.intrinsic.com/colors/1.4.1/1.4.2 So that is still ongoing and pinning to v1.4.0 (using resolutions or your package.json and package-lock.json/yarn.lock files if directly...
> They’d erase the package as a whole, easier to just downgrade and hold. @Solixity since the left-pad drama happened no, you can not delete releases and packages after a...