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

fix(deps): update qrcode.react to 4.0.1 #630

Open
wants to merge 1 commit into
base: development
Choose a base branch
from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Sep 10, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
qrcode.react (source) 3.1.0 -> 4.0.1 age adoption passing confidence

Release Notes

zpao/qrcode.react (qrcode.react)

v4.0.1

Compare Source

Fixed
  • Corrected issue with loading types in Typescript when configured with "moduleResolution": "Bundler" or "module": "ESNext". (#​368)

v4.0.0

Compare Source

Added
  • Added proper support for ref, enabling direct access for underlying canvas or svg nodes. This also resulted in much more accurate type defitions. (#​202)
  • Added support for marginSize prop, replacing the now deprecated includeMargin. This enables margins of any value, not just 0 or 4. (#​281)
  • Added Support for Setting Image Opacity via imageSettings.opacity (#​292)
  • Added minVersion prop to give better control over QR Code generated (#​323)
  • Added support for specifying cross-origin for embedded images via imageSettings.crossOrigin. (#​324)
Changed
  • Improved accessibility for QRCodeSVG by rendering a <title> node instead of setting a title attribute. (#​284)
  • Improved accessibility with explicit role set on rendered SVG and Canvas. (#​321)
  • Improved documentation (#​358)
  • Used better types in TypeScript for ErrorCorrectionLevel, resulting in better developer experience. (#​291)
Deprecated
  • The includeMargin prop has been deprecated in favor of marginSize. (#​281)
Removed
  • Removed default export which was deprecated in v3. (#​208)
  • Remove explicit style prop. This still works identically as it was passed through and the type definitions are unaffected as they were improved via the ref changes (#​357)
Fixed
  • Improved support for dual publishing of ESM/CJS modules for better compatibility with tools. (#​301)
  • Set explicit display names for improved debugging experience. (#​304)
  • Improved SVG compatibility by using href in place of xlink:href for embedded images. (#​336)
  • Mitigated warnings when using QRCodeSVG in server components (#​352)

v3.2.0

Compare Source

Fixed
  • Improved support for dual publishing of ESM/CJS modules for better compatibility with tools. (#​301, #​368)
  • Mitigated warnings when using QRCodeSVG in server components (#​352)
Changed
  • Added @deprecated JSDoc to default export for additional visibility in editors to TypeScript users.

Configuration

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

🚦 Automerge: Enabled.

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.

Copy link
Author

renovate bot commented Sep 10, 2024

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @typescript-eslint/[email protected]
npm error Found: [email protected]
npm error node_modules/eslint
npm error   dev eslint@"^9.2.0" from the root project
npm error   peer eslint@"^7.5.0 || ^8.0.0 || ^9.0.0" from @babel/[email protected]
npm error   node_modules/@babel/eslint-parser
npm error     dev @babel/eslint-parser@"^7.24.5" from the root project
npm error   5 more (@eslint-community/eslint-utils, eslint-config-erb, ...)
npm error
npm error Could not resolve dependency:
npm error peer eslint@"^8.56.0" from @typescript-eslint/[email protected]
npm error node_modules/@typescript-eslint/eslint-plugin
npm error   dev @typescript-eslint/eslint-plugin@"^7.8.0" from the root project
npm error   peer @typescript-eslint/eslint-plugin@"^7.0.0" from [email protected]
npm error   node_modules/eslint-config-airbnb-typescript
npm error     dev eslint-config-airbnb-typescript@"^18.0.0" from the root project
npm error   1 more (eslint-plugin-jest)
npm error
npm error Conflicting peer dependency: [email protected]
npm error node_modules/eslint
npm error   peer eslint@"^8.56.0" from @typescript-eslint/[email protected]
npm error   node_modules/@typescript-eslint/eslint-plugin
npm error     dev @typescript-eslint/eslint-plugin@"^7.8.0" from the root project
npm error     peer @typescript-eslint/eslint-plugin@"^7.0.0" from [email protected]
npm error     node_modules/eslint-config-airbnb-typescript
npm error       dev eslint-config-airbnb-typescript@"^18.0.0" from the root project
npm error     1 more (eslint-plugin-jest)
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /tmp/renovate/cache/others/npm/_logs/2024-09-10T13_03_55_958Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-09-10T13_03_55_958Z-debug-0.log

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant