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
fix(between): added error case when to/from unit is differs from mix/max #511
Commits on May 10, 2020
-
chore(library): update dependencies
Update dependencies and fix new flow error in triangle.test.js
-
refactor(stripunit): fully deprecate returnUnit
Fully deprecate returnUnit functionality and refactor return.
-
refactor(readablecolor): make strict mode default
Make strict mode default when passing custom colors.
-
build(babel): enable bugfix: true
Enable bugfix:true in build and target explicit browser list
-
-
-
-
-
feat(fontface): now defaults to looking for local font first
Default is now to look for a local font of the same family-name before downloading. Can be turned off by passing null to localFonts. BREAKING CHANGE: localFont will now be populated by default and may have unexpected behavior.
-
feat(important): important helper for module rule specificity
important helper for targeting specific rules in module returns for adding `!important`-level specificity.
-
-
-
fix(triangle): triangle now properly supports inherit
triangle now returns properties in a way that allows inherit to work by declaring an individual side for the triangle color.
Commits on May 11, 2020
-
feat(cssvar): allow a default value for cssVar
Allow the user to pass a default value to cssVar for when a variable is not found.
Commits on May 15, 2020
-
fix(between): added error case when to/from unit is different than mi…
…n/max Added an error case when the unit for to/fromSize is different than min/maxScreen. This was causing bad calculations based on the differing scales. BREAKING CHANGE: If you were using a mix of unit and unitless measure or working with different units with similar scales (em/rem) you will now get an error where you may have been getting a seemingly valid calculation. fix #445
-