Skip to content
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 dependency @vibrant/quantizer-mmcq to v4 #23500

Draft
wants to merge 1 commit into
base: dev
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Dec 29, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@vibrant/quantizer-mmcq (source) 3.2.1-alpha.1 -> 4.0.0 age adoption passing confidence

Release Notes

Vibrant-Colors/node-vibrant (@​vibrant/quantizer-mmcq)

v4.0.0

Compare Source

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

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot added the Dependencies Pull requests that update a dependency file label Dec 29, 2024
@silamon silamon marked this pull request as draft December 30, 2024 10:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants