fix(deps): update all non-major dependencies#233
Open
renovate[bot] wants to merge 1 commit intotrunkfrom
Open
Conversation
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
11 times, most recently
from
0f769f6 to
7c237d2
Compare
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
9 times, most recently
from
e829131 to
290254e
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
8 times, most recently
from
e91a628 to
b204c53
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
1e04aeb to
ab4be12
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
7 times, most recently
from
8459e05 to
73b9b3b
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
9 times, most recently
from
fa8c703 to
3f4e77c
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
7 times, most recently
from
fc75163 to
78bd5b1
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
3 times, most recently
from
119abd6 to
90fe223
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
90fe223 to
cefcd15
Compare
This file contains hidden or 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
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.
This PR contains the following updates:
^1.17.1→^1.19.9^1.1.10→^1.1.11^4.1.24→^4.1.396.0.1→6.0.4^13.6.0→^13.9.0^0.6.0-alpha.1→^0.6.1^5.1.1→^5.6.3^1.39.8→^1.44.09.32.0→9.39.3^4.8.10→^4.12.25.62.0→5.85.01.12.2→1.13.6^4.17.21→^4.17.23^3.0.3→^3.0.43.6.2→3.8.14.20.3→4.21.07.0.8→7.3.1^3.5.18→^3.5.293.5.18→3.5.29^4.5.1→^4.6.43.0.4→3.2.5^4.0.14→^4.3.6Release Notes
honojs/node-server (@hono/node-server)
v1.19.9Compare Source
What's Changed
Full Changelog: honojs/node-server@v1.19.8...v1.19.9
v1.19.8Compare Source
What's Changed
New Contributors
Full Changelog: honojs/node-server@v1.19.7...v1.19.8
v1.19.7Compare Source
What's Changed
configVersionto bun.lock by @yusukebe in #291New Contributors
Full Changelog: honojs/node-server@v1.19.6...v1.19.7
texel-org/color (@texel/color)
v1.1.11Compare Source
thi-ng/umbrella (@thi.ng/random)
v4.1.39Compare Source
v4.1.38Compare Source
v4.1.37Compare Source
v4.1.36Compare Source
v4.1.35Compare Source
v4.1.34Compare Source
v4.1.33Compare Source
vitejs/vite-plugin-vue (@vitejs/plugin-vue)
v6.0.4Bug Fixes
Miscellaneous Chores
v6.0.3Features
Bug Fixes
Performance Improvements
Miscellaneous Chores
v6.0.2Bug Fixes
Miscellaneous Chores
color-js/color.js (colorjs.io)
v0.6.1Compare Source
Just a small patch to fix a TS issue!
What's Changed
New Contributors
Full Changelog: color-js/color.js@v0.6.0...v0.6.1
v0.6.0Compare Source
This has taken a while and three pre-releases, but we wanted to make sure we got everything right.
This is likely to be the last v0.x release, as Color.js is certainly mature enough to go to v1 in the next major version.
Speaking of maturity…
⬇️ Over 100 million downloads! 🤯
Color.js has now been downloaded over 114 million times on npm!
The rate of increase is still accelerating, currently at 3.5 million downloads per week!
We even had to automate updating the number in our README so we could have a chance to keep up (thanks @MysteryBlokHed!).
Making Color.js sustainable
You may have noticed we removed ads from the Color.js website a while back.
While Carbon ads were the good kind of ads (relevant, not intrusive), it was not really worth it, they barely made enough to cover costs like the domain name etc.
Instead, we have started an Open Collective that you can fund directly.
If your company depends on Color.js in any way, it is in your best interest to ensure its future is sustainable.
Once there are enough sponsors, we plan to feature them prominently on our website and README, so if you want to be among the first ones to get your name in there, now’s the chance:
Breaking changes
There are a number of breaking changes in this release, but they should only negatively affect some pretty specialized use cases.
nullinstead ofNaNto representnonevaluesAs announced in v0.5.0, we have now switched to using
nullinstead ofNaNto representnonevalues (naturally occurring when converting achromatic colors to certain color spaces).Not only is
nullconceptually closer, but since CSS also now has aNaNvalue, this change allows us to represent it properly, using an actualNaNvalue.NaNcontinues to be parsed (and becomesNaNin JS). Instead of being serialized asNaN(which is invalid in CSS), it is serialized ascalc(NaN)which is a valid CSS coordinate. For roundtripping to work properly, this also means we now parsecalc(NaN)as well. Slippery slope? We’ll see. 😁(by @leaverou in
cdf6f0d, @facelessuser in #476, @mysteryblokhed in #530)Programmatically detecting how
noneis representedIf you are working with any code that needs to handle
Colorinstances/objects generically, without knowing which version of Color.js they come from, you can detect which value is being used and use that instead of a hardcodednullorNaN:Plain numbers instead of
Numberobjects for coordinatesPreviously, coordinates would be parsed into
Numberobjects so they could retain metadata about their parsing. From this release onwards, they are plain number primitives, which results in both performance improvements, and improved DX for most cases.Instead, parsing metadata is passed around as a separate object, and stored on
Colorinstances undercolor.parseMeta. This happens automatically in the OOP API, but users need to explicitly opt-in when using the procedural API, since that is optimized for high performance use cases.In addition, this metadata is now far more elaborate and can pretty much recreate the format parsed. Which brings us to…
Colors now reserialized in the format parsed
We heard you! This has been a longstanding pain point, and it is now fixed. If you’re parsing a hex color, it will be serialized back to a hex color by default. If you’re specifying your chroma in percentages, percentages you’ll get back. If for some reason, you’re parsing a legacy comma-separated color, lo and behold, you can modify it and get back a legacy comma-separated color without lifting a finger!
Caveats:
parseMetaobject explicitly.format(orformat: "default") for the color space default, which gives you the previous behavior.Other big improvements
New color spaces
More control over serialization
You can now specify a format from any color space in
serialize()/color.toString()without having to convert the color to a different color space.There is even a new function,
ColorSpace.findFormat()to find a format that matches certain criteria across all registered color spaces.Another big pain point was that the way Color.js did serialization made simple things easy (by having sensible defaults and a wide range of predefined formats) and complex things possible (by allowing entirely custom formats to be specified), but the in-between was not smooth at all: the moment you needed anything custom, the only way was to recreate a whole format, which is a UX antipattern.
Starting with this release, you can now specify a lot more granular options for serialization, without having to redefine a format:
coordswith an array of coord types (e.g.["<percentage>", "<number>[0, 100]", "<angle>"]). Anyundefinedvalues will just get the default type, so you can even do things like[, "<percentage>", ]to e.g. make OKLCh chroma a percentage without having to respecify the default type of any other coord.alphato control display and type of alpha:alpha: truealpha: falsealpha: "<percentage>"alpha: {include: true, type: "<percentage>"}Switching from TypeScript types to JSDoc
You may have noticed that our API docs had not been great in the past. This is because we were describing types in
.d.tsfiles, but documentation was in JSDoc comments. However (the otherwise lovely) Typedoc expects a single source of truth for both, which would mean either having untyped API docs, or API docs with only types. It also meant that we had to maintain Color.js’s pretty extensive API in two places, which did not scale.With this release we went all in on JSDoc, thanks to @MysteryBlokHed’s monumental effort in #540.
For complex types, we are still using
.d.tsfiles with the new JSDoc@importsyntax so that JSDoc is still the source of truth (by @MysteryBlokHed and @lloydk in #686).This does not affect you, whether you are consuming Color.js via TS or JS, types should still just work. You may, however, see better inline documentation!
Other Color.js Initiatives
Color Apps
We have also moved our Color apps (which also serve as Color.js demos) into their own repo and domain: apps.colorjs.io.
If you have links to these, there’s nothing to worry about: the old URL still works (it just redirects to the new one).
There is also a new app:
These are rather esoteric, but they have been used in CSS Working Group research to help figure out what gamut mapping algorithm to use natively in CSS.
Color Palettes
Another experimental project under the Color.js umbrella is Color Palettes,
which aims to analyze designer-created color palettes in a variety of color spaces, as an attempt to understand how to generate them
and document what patterns are prominent.
You may (or may not) be surprised to find that they are not regular in any color space, not even perceptually uniform ones.
This project is still in its infancy (I would not even call it alpha), but we are excited about its potential.
Color Elements
You may have noticed our three experimental custom elements in the past — or maybe not, as they were very experimental and thus not featured very prominently.
These have now been split into a separate project, and a separate domain: elements.colorjs.io and expanded into a library of 10 web components for building color-related apps (the first library of its kind to our knowledge).
They are still very experimental, but way more polished than their previous state.
If you were referencing these from their previous URL, there is a redirect in place, but do note their tag names and API have changed.
Color Elements were originally developed for our own Color Apps and the Color Palettes project, so these projects also serve as demos for them.
Other changes
API changes
Color parsing & formatting
Color.try()/tryColor(): A common request has been a function that gracefully parses colors, without throwing if there is an error. This version adds exactly that:tryColor()/Color.try()(by @LeaVerou in #664)0.30000000000000004? Our default number formatting now attempts to limit IEEE 754 precision issues.parse()now clamps alpha as well, just like theColorconstructor (by @LeaVerou)Color difference
deltas()functions for getting coordinate/alpha differences between two colors in any color space. (@LeaVerou in #532)OK2, believed to be more perceptually uniform (by @svgeesus in #486)Getting and setting coordinates
get()/set()/setAll()now support alpha as well (by @leaverou)getAll()now supports an optionaloptionsparameter object withspaceandprecisionas possible keys (by @DmitrySharabin in #548)Exports
spacesexport of/fnand the new/spacestop-level export. (by @LeaVerou in #663, with types by @MysteryBlokHed in #668)colorjs.io/fn) now also available with ESM exports (by @MysteryBlokHed in #606)/srcexport to import Color.js's source code directly as ESM, when there is no suitable high-level export for what you need (by @LeaVerou in #663, with types by @MysteryBlokHed in #668)Performance
API changes for spec compliance
color(ictcp ...)toictcp(...)per CSS Color HDR (by @svgeesus in #646)color(jzazbz ...)tojzazbz(...), andcolor(jzczhz ...)tojzczhz(...)per CSS Color HDR (by @svgeesus in #647)display-p3-linearsince it is now in CSS Color 4 (i.e.color(--display-p3-linear ...)→color(display-p3-linear ...)(by @svgeesus inc90fe38). Not a breaking change, as both are still supported.rec2020; rename previous implementation as scene-referred--rec2020-oetf(by @svgeesus in #669)Docs
Website
Bug fixes
Object-oriented functions now work between different sources of Color.js (by @MysteryBlokHed in #605)
Fix serialization of negative percentages (by @lloydk in #554)
Handle negative square roots in a sane manner for Rec. 2100 HLG (by @facelessuser in #575)
Do not use HSL normalized saturation and hue for certain spaces (by @facelessuser in #582)
Avoid mutating arguments passed to the Color constructor (by @MysteryBlokHed in #603)
Fix parsing 7-character hex colors (by @kleinfreund in #616)
Fix parsing of percentage values for color spaces with coords that have a range property with a minimum value less than 0 (e.g. acescc) (by @lloydk in #619)
CAM16 and HCT hues are now correctly set to
nullwhen chroma is near zero (by @facelessuser in #644)Fix issues with creating custom color spaces (by @sidewayss and @LeaVerou in #628)
Don't clamp negative values in Absolute XYZ D65 (by @svgeesus in #613)
Adjust calculations in Jzazbz and fix Jzazbz and JzCzhz reference ranges (by @svgeesus in #634 #635)
Ensure Prophoto and Rec2020 spaces handle negative values (by @lloydk in #640)
Don't throw for unknown coords when space accessors are used (by @LeaVerou)
In
toGamut(), better handle the case when JND equals 0 (by @facelessuser in #659)Improvements to types
colorSpace.isUnboundedproperty (by @lloydk in #503)setAll(),getAll(),toGamut(),deltas(), and add types for CSS color keywords (by @lloydk in #520 #544 #545 #546 #598)multiplyMatricestypes and update implementation to pass all tests (by @epsilonError in #580 #631)null(by @lloydk)darken()/lighten()functions on theColorclass (by @lloydk in #654)@typedefwith@importwhere relevant to improve DX and overall quality of generated.d.tsfiles (by @MysteryBlokHed and @lloydk in #686)For contributors
--servetowatch:html(by @jamesnw in #467)f02ce7f)New Contributors
Full Changelog: color-js/color.js@v0.5.2...v0.6.0
toss/es-toolkit (es-toolkit)
v1.44.0Compare Source
Released on January 16th, 2026.
shouldRetryoption toretryfunction. ([#1585])isEmptyObjectpredicate function. ([#1584])isNumberpredicate function.AggregateError. ([#1563])flattenObjectto retain empty objects and arrays.clonefunction.cloneerror when cloning object with null prototype. ([#1570])compat/cloneDeepandcloneDeepWithto clone null-prototype objects as regular objects. ([#1562])compat/clampto ensure consistency with lodash. ([#1555])intersectionfilter callback for consistency. ([#1582])cloneDeepJSDoc examples. ([#1583])We sincerely thank @raon0211, @dayongkr, @eunwoo-levi, @matt-oakes, @T3sT3ro, and @D-Sketon for their contributions. We appreciate your great efforts!
v1.43.0Compare Source
Released on December 12th, 2025.
mergeto handle arrays and objects consistently, and to match lodash's behavior with date values and array-like objects. ([#1553], [#1542], [#1548])isMatchandisMatchWithto match lodash's behavior.intersectionByimplementation and removed duplicates when the mapper produces the same values. ([#1528])throttleworking like debounce.toSnakeCaseKeys,toCamelCaseKeysfor edge cases and improved type inference for uppercase keys. ([#1538])camelCase,kebabCase,lowerCase,snakeCase,startCase,upperCase) to match lodash's behavior. ([#1525])compat/templateto disable ES interpolation when custominterpolateis provided. ([#1527])differenceBydocumentation. ([#1543])deburrto use arrays to construct the deburrMap. ([#1526])We sincerely thank @dayongkr, @raon0211, @wo-o29, @Yeom-JinHo, @Copilot, @oshosh, @vbfox, @sukvvon, @sankeyangshu, @D-Sketon, @seo-rii for their contributions. We appreciate your great efforts!
v1.42.0Compare Source
Released on November 17th, 2025.
filterAsync,flatMapAsync,forEachAsync,mapAsync,reduceAsync, andlimitAsyncfor handling asynchronous operations.ThrottleOptionsandDebounceOptionsinterfaces for better type support.isFiniteto implement type predicate to narrow type to number.isSafeIntegerto implement type predicate to narrow type to number.omitto prevent adding index properties to array-like objects.mergeWithto remove unnecessary nullish coalescing for 100% branch coverage.compat/updateWithto remove unreachable code and add prototype pollution test.compat/mergeWith,compat/unset,get,toMerged,mergeWith, andcompat/intersectionBywith additional edge cases and security tests.We sincerely thank @Debbl, @wo-o29, @raon0211, @Yeom-JinHo, @sukvvon, and @D-Sketon for their contributions. We appreciate your great efforts!
v1.41.0Compare Source
Released on October 24th, 2025.
throttleto preservethiscontext when called as a method.partitionfunction.omitto support runtime-determined key arrays with proper overloads.defaultsin compatibility layer to properly handle undefined and null sources.toSnakeCaseKeysandtoCamelCaseKeysto correctly return types for non-plain objects.toMergedandmergeWithto properly handle shared objects in merge logic.compat/unionto support array-like objects.compat/updateWithto usegetfor value retrieval in updater function.isMatchandisMatchWith.findandfindLastby simplifying logic and removing unnecessary checks.takeRightby improving test coverage and removing redundant checks.curryandcurryRightby removing unnecessary type assertions.isEqualWithandmapKeysby removing unnecessary type assertions.meanByby removing intermediate array creation.We sincerely thank @the5thbeatle, @wo-o29, @hwibaski, @manudeli, @raon0211, @dayongkr, @D-Sketon, @yoouungyoung, @Dohun-choi, @sukvvon, @zoulou00, and @sen2y for their contributions. We appreciate your great efforts!
v1.40.0Compare Source
Released on October 8th, 2025.
sumByto pass the element index to thegetValuecallback function.uniqfunction.cloneDeepWithto handle runtime errors in environments without Blob support and correctly clone Boolean, Number, and String objects.omitto avoid unnecessary deep cloning, improving performance.toCamelCaseKeysto properly handle PascalCase type conversion.toPathto correctly handle arrays and non-string inputs.repeatto validate and handle invalid repeat counts.sortedIndexByto properly handle default iteratee.somepredicate check to correctly handle null and undefined cases.compat/unsetwith nonexistent paths.We sincerely thank @wo-o29, @D-Sketon, @HidenLee, @yoouung, [@manudeli](https://redirect.githu