-
Notifications
You must be signed in to change notification settings - Fork 30
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
v1.0.0 release #139
v1.0.0 release #139
Conversation
That would seem consistent with 4.7.4. Serializing values of the color() function |
Yes. Currently (as of |
…pendencies: * Use `esbuild` instead of `rollup` to build separate ESM/CJS/IIFE bundles; * Update `eslint` to work with the new setup * Run tests without passing the sources through the `esm` package
… properties. Changed methods: * defineMode() => useMode(); * getModeDefinition() => getMode(); Changes in color space definition: * input{} => fromMode{} * output{} => toMode{} * parsers[] => parse[] * serialize: don't include the awkward "color(" part
…vors: * 'culori' — full library, with all color spaces pre-registered; * 'culori/css' — with just the css-color-4-related color spaces; * 'culori/fn' - tree-shakeable collection of functions, no color spaces pre-registered.
Decided to make a less ambitious |
Thanks @svgeesus for keeping me in the loop! I will open an issue for the |
Code
Breaking changes:
xyz
refer to D65 XYZ instead of D50 XYZ (ref)xyz
ascolor(xyz)
Outstanding issues:
Documentation