-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update chroma-js to the latest version 🚀 #197
Closed
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Version 1.3.1 just got published. |
Version 1.3.3 just got published.Update to this version instead 🚀 Release Noteschroma 1.3.3
|
Version 1.3.4 just got published.Update to this version instead 🚀 CommitsThe new version differs by 11 commits.
See the full diff |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Version 1.3.0 of chroma-js just got published.
The version 1.3.0 is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of chroma-js.
Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Release Notes
chroma 1.3.0Commits
The new version differs by 39 commits .
d819961
bumped version, changelog
d954c47
chroma got slightly larger
9d4f742
updated documentation
1c804fa
copy build files to docs/libs
deb5561
don't convert #3 to github issue link
bf85490
updated tests for high precision
2899178
simplified implementation
eed5038
keeping RGB channels as float internally for higher precision
e2f9aaf
added chroma.delta-e
721a754
making sure hues are averaged correctly
8691a64
added cubehelix test
d726b03
added chroma js to docs
bd6659f
new method for computing distances between 2 colors
026da25
chroma.scale allows disabling of internal cache
6f57e83
color.set returns new chroma instance
There are 39 commits in total. See the full diff.
Not sure how things should work exactly?
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot 🌴