New export type broke lots of apps about tinycolor HOT 8 CLOSED

@steezeburger since it sounds like you're using yarn you can use resolutions https://classic.yarnpkg.com/en/docs/selective-version-resolutions/

Adding a resolution to your package.json and then running yarn install should fix it until they release a new version.

// package.json
{
  "resolutions": {
    "@ant-design/colors": "5.0.0"
  }
}

You might also be able to add @ant-design/colors to your dependencies pinned to "5.0.0" and get that specific version instead of 5.1.0

see also - ant-design/ant-design-colors#77

from tinycolor.

🎉 This issue has been resolved in version 3.3.1 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

from tinycolor.

same issue, revert 3.3.0 please!

from tinycolor.

@scttcper Thanks a lot for the hotfix

from tinycolor.

same issue 3.3.1

from tinycolor.

I'm also having this issue again, but my yarn.lock shows the latest for ant-design-color, which is using 3.3.1 of tinycolor. Did something else happen recently to start causing this issue again?

from tinycolor.

@steezeburger i think its ant-design-color this time, I would use 5.0.0 instead. 5.1.0 changed something with imports that was then reverted without a patch version yet. https://github.com/ant-design/ant-design-colors/releases/tag/v5.1.0

unreleased revert commit - ant-design/ant-design-colors#75

from tinycolor.

@scttcper thanks for the quick reply!

I will try to use 5.0.0. Unfortunately I am not using ant-design-colors directly. I am using antd, which requires ant-design-colors, which requires your library. antd's package.json specifies ^5.0.0 for ant-design-colors, so it installs 5.1.0. I am not a front end guy, is it possible to define sub dependency versions so I can explicitly install 5.0.1?

I of course could fork antd, but I do not want to begin maintaining that fork.

from tinycolor.