Bump @vibrant/image-node from 3.2.1-alpha.1 to 4.0.0 #24
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
![dependabot[bot]](https://avatars.githubusercontent.com/in/29110?s=60&v=4){kind=small}
Bumps [@vibrant/image-node](https://github.com/Vibrant-Colors/node-vibrant/tree/HEAD/packages/vibrant-image-node) from 3.2.1-alpha.1 to 4.0.0. - [Release notes](https://github.com/Vibrant-Colors/node-vibrant/releases) - [Changelog](https://github.com/Vibrant-Colors/node-vibrant/blob/main/CHANGELOG.md) - [Commits](https://github.com/Vibrant-Colors/node-vibrant/commits/v4.0.0/packages/vibrant-image-node) --- updated-dependencies: - dependency-name: "@vibrant/image-node" dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <[email protected]>
dependabot
bot
added
dependencies
|
@dependabot ignore this dependency
Thanks,
Todd
On Dec 31, 2024, at 11:12 PM, dependabot[bot] ***@***.***> wrote:
Bumps @vibrant/image-node from 3.2.1-alpha.1 to 4.0.0.
Release notes
Sourced from @vibrant/image-node's releases.
v4.0.0
The first stable release in 4 years!
This is a huge release with a ton of internal stability improvements, bug fixes, and more.
There's even a docs site now: https://vibrant.dev
image.png (view on web)
The codebase has never been in as good as a place as it is today; even in the early 3.15 days.
Breaking Changes
- You now must import from node-vibrant/browser, node-vibrant/node, or node-vibrant/worker to get the correct environment-specific implementation
- Vibrant class is now a named export
- Node 18+ is now required
- ES5 support is dropped
- Vibrant.getPalette no longer accepts a name or callback API
- Please migrate to the promise-based API to replace the callback API
- Please let us know if you were using the name API: https://github.com/Vibrant-Colors/node-vibrant/issues
- It was unclear how this was used in practice. We can reconsider adding it back if there's usecases I wasn't aware of
- Vibrant.getPalettes no longer accepts a names or callback API
- Please migrate to the promise-based API to replace the callback API
- Please let us know if you were using the names API: https://github.com/Vibrant-Colors/node-vibrant/issues
- It was unclear how this was used in practice. We can reconsider adding it back if there's usecases I wasn't aware of
- Builder.getSwatches alias was removed in favor of calling Builder.getPalette
- Removed the deprecated Builder.getHex API, use the Builder.hex property instead
- Removed the deprecated Builder.getPopulation API, use the Builder.population property instead
- Removed the deprecated Builder.getHsl API, use the Builder.hsl property instead
- Removed the deprecated Builder.getRgb API, use the Builder.rgb property instead
- Workers are imported differently using the ?worker import fix alias
Changelog
Sourced from @vibrant/image-node's changelog.
v4.0.0
node-vibrant's internal packaging is now vastly more stable and improved. We'll continue to ship the default package with the same API as before, but now you can also import individual modules for more control over your environment.
Breaking Changes
- You now must import from node-vibrant/browser, node-vibrant/node, or node-vibrant/worker to get the correct environment-specific implementation
- Vibrant class is now a named export
- Node 18+ is now required
- ES5 support is dropped
- Vibrant.getPalette no longer accepts a name or callback API
- Please migrate to the promise-based API to replace the callback API
- Please let us know if you were using the name API: https://github.com/Vibrant-Colors/node-vibrant/issues
- It was unclear how this was used in practice. We can reconsider adding it back if there's usecases I wasn't aware of
- Vibrant.getPalettes no longer accepts a names or callback API
- Please migrate to the promise-based API to replace the callback API
- Please let us know if you were using the names API: https://github.com/Vibrant-Colors/node-vibrant/issues
- It was unclear how this was used in practice. We can reconsider adding it back if there's usecases I wasn't aware of
- Builder.getSwatches alias was removed in favor of calling Builder.getPalette
- Removed the deprecated Builder.getHex API, use the Builder.hex property instead
- Removed the deprecated Builder.getPopulation API, use the Builder.population property instead
- Removed the deprecated Builder.getHsl API, use the Builder.hsl property instead
- Removed the deprecated Builder.getRgb API, use the Builder.rgb property instead
- Workers are imported differently using the ?worker import fix alias
v3.2.0
node-vibrant is now a monorepo. Building blocks of node-vibrant has been separated into multiple small packages under @vibrant/* scope. The goal is to make it more flexible, allowing alternative algorithms, additional image format support and etc to be implemented by 3rd party packages.
The node-vibrant package still provides default experience out-of-box.
Breaking Changes
- strickNullChecks flag is now enabled.
- Prebuilt bundle will not be provided. You should use your own webpack workflow.
3.1.0
- Fix empty swatches sometimes showing up for images
- Update deps
- Moved from Bluebird to native promises
- Fix issue with dist folder not appearing on install
- Fix issue with images not loading properly
3.0.0
New WebWorker support in v3.0
Quantization is the most time-consuming stage in node-vibrant. In v3.0, the quantization can be run in the WebWorker to avoid freezing the UI thread.
... (truncated)
Commits
- 7709dd5 v4.0.0
- 24604a0 chore: fix issues with sherif
- 9d64d9d v4.0.0-beta.1
- 10bae22 chore: add publint strict
- f9c3880 chore: fix link to correct domain in package json
- f82f260 chore: fix CI
- eef47ee chore: fix issues with Nx and TanStack Config
- 3cd7210 chore: format docs files
- 09b13c8 chore: add config for docs generation
- 81510b2 chore: fix more TSC usage on test files
- Additional commits viewable in compare view
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
- @dependabot rebase will rebase this PR
- @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
- @dependabot merge will merge this PR after your CI passes on it
- @dependabot squash and merge will squash and merge this PR after your CI passes on it
- @dependabot cancel merge will cancel a previously requested merge and block automerging
- @dependabot reopen will reopen this PR if it is closed
- @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
- @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
- @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
- @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
- @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
You can view, comment on, or merge this pull request online at:
#24
Commit Summary
- e06a6c0 Bump @vibrant/image-node from 3.2.1-alpha.1 to 4.0.0
File Changes
(2 files)
- M package-lock.json (782)
- M package.json (2)
Patch Links:
- https://github.com/thlucas1/homeassistantcomponent_soundtouchplus_card/pull/24.patch
- https://github.com/thlucas1/homeassistantcomponent_soundtouchplus_card/pull/24.diff
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>
|
|
OK, I won't notify you about @vibrant/image-node again, unless you re-open this PR. |
dependabot
bot
deleted the
dependabot/npm_and_yarn/vibrant/image-node-4.0.0
branch
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.
Bumps @vibrant/image-node from 3.2.1-alpha.1 to 4.0.0.
Release notes
Sourced from
@vibrant/image-node's releases.Changelog
Sourced from
@vibrant/image-node's changelog.... (truncated)
Commits
7709dd5v4.0.024604a0chore: fix issues with sherif9d64d9dv4.0.0-beta.110bae22chore: add publint strictf9c3880chore: fix link to correct domain in package jsonf82f260chore: fix CIeef47eechore: fix issues with Nx and TanStack Config3cd7210chore: format docs files09b13c8chore: add config for docs generation81510b2chore: fix more TSC usage on test filesDependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)