fix(deps): update dependency react-slick to v0.30.2

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
react-slick (source)	0.23.2 -> 0.30.2

---

Release Notes

akiran/react-slick (react-slick)

v0.30.2

Compare Source

Fixed issues #​2076 and #​2344

v0.30.1

Compare Source

Fixed issues #​1874 and #​2315

v0.30.0

Compare Source

• Fixed #​1813
• Migrated tests from enzyme to react-testing-library
• Migrated examples from class components to function components

v0.29.0

Compare Source

Upgraded dependencies to support React 18

v0.28.1

Compare Source

v0.28.0

Compare Source

Fixes for #​1650

Merged PR's: #​1967 #​1971

v0.27.14

Compare Source

Fixed #​1830

v0.27.13

Compare Source

v0.27.12

Compare Source

v0.27.11

Compare Source

v0.27.10

Compare Source

v0.27.9

Compare Source

v0.27.8

Compare Source

v0.27.7

Compare Source

v0.27.6

Compare Source

v0.27.5

Compare Source

v0.27.4

Compare Source

Fixed an issue with uneven sets in focusOnSelect mode

v0.27.3

Compare Source

Fixed bug: slick-current set on the last slide instead of the first slide when the first slide is dragged left to right in infinite=false mode

v0.27.2

Compare Source

Fixed bugs

1. slick-current class not properly set on slides in infinite=false mode
2. FocusOnSelect on the first slide doesn't work when infinite=false

v0.27.1

Compare Source

Refactor to remove UNSAFE_componentWillMount usage

v0.27.0

Compare Source

Removed usage of findDOMNode (deprecated API)

Merged PR: #​1442

v0.26.1

Compare Source

Bug fixes and improvements

• Disconnecting ResizeObserver to fix memory leak issue
• Fix an issue with image loading. #​1356
• undoing #​1781 as it is breaking rtl

Merged PRs
#​1703 #​1723

v0.26.0

Compare Source

Bug fixes & improvements

• Removed unnecessary vendor prefixes
• Fix an issue with unslick in responsive mode. #​1663
• Fix an issue with ltr

v0.25.2

Compare Source

v0.25.1

Compare Source

v0.25.0

Compare Source

Added UNSAFE_ prefix to deprecated lifecycle methods to avoid warnings from React 16.9

Bug fixes
#​1562

v0.24.0

Compare Source

• Updated webpack and babel version
• Bug fix for asNavFor feature

---

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 has been generated by Mend Renovate. View repository job log here.

[renovate]

⚠ 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 ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: react-redux@7.0.3
npm ERR! Found: redux@5.0.1
npm ERR! node_modules/redux
npm ERR!   dev redux@"5.0.1" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer redux@"^2.0.0 || ^3.0.0 || ^4.0.0-0" from react-redux@7.0.3
npm ERR! node_modules/react-redux
npm ERR!   dev react-redux@"7.0.3" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: redux@4.2.1
npm ERR! node_modules/redux
npm ERR!   peer redux@"^2.0.0 || ^3.0.0 || ^4.0.0-0" from react-redux@7.0.3
npm ERR!   node_modules/react-redux
npm ERR!     dev react-redux@"7.0.3" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /tmp/renovate/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate/cache/others/npm/_logs/2024-02-17T10_45_49_106Z-debug-0.log

[renovate]

⚠️ 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 ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: react-reveal@1.2.2
npm ERR! Found: react@18.3.1
npm ERR! node_modules/react
npm ERR!   react@"18.3.1" from the root project
npm ERR!   peer react@"^18.3.1" from react-dom@18.3.1
npm ERR!   node_modules/react-dom
npm ERR!     react-dom@"18.3.1" from the root project
npm ERR!     peer react-dom@">=16.8" from react-router-dom@6.23.1
npm ERR!     node_modules/react-router-dom
npm ERR!       react-router-dom@"6.23.1" from the root project
npm ERR!     2 more (react-transition-group, react-slick)
npm ERR!   6 more (react-redux, react-router, react-router-dom, ...)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer react@"^15.3.0 || ^16.0.0" from react-reveal@1.2.2
npm ERR! node_modules/react-reveal
npm ERR!   react-reveal@"1.2.2" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: react@16.14.0
npm ERR! node_modules/react
npm ERR!   peer react@"^15.3.0 || ^16.0.0" from react-reveal@1.2.2
npm ERR!   node_modules/react-reveal
npm ERR!     react-reveal@"1.2.2" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /tmp/renovate/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate/cache/others/npm/_logs/2024-05-12T17_06_52_233Z-debug-0.log