[Snyk] Upgrade: , htm, preact-render-to-string, redux, react-redux, react-router, react-router-dom

[NOUIY]

Snyk has created this PR to upgrade multiple dependencies.

👯 The following dependencies are linked and will therefore be updated together.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

Name	Versions	Released on

@material-ui/core
from 4.9.5 to 4.12.4 | 24 versions ahead of your current version | 2 years ago
on 2022-04-03
htm
from 2.1.1 to 2.2.1 | 2 versions ahead of your current version | 5 years ago
on 2019-07-31
preact-render-to-string
from 5.2.1 to 5.2.6 | 5 versions ahead of your current version | 2 years ago
on 2022-10-23
redux
from 4.2.0 to 4.2.1 | 1 version ahead of your current version | 2 years ago
on 2023-01-28
react-redux
from 7.2.8 to 7.2.9 | 1 version ahead of your current version | 2 years ago
on 2022-09-23
react-router
from 5.3.3 to 5.3.4 | 1 version ahead of your current version | 2 years ago
on 2022-10-02
react-router-dom
from 5.3.3 to 5.3.4 | 1 version ahead of your current version | 2 years ago
on 2022-10-02

Release notes

Package name: @material-ui/core

• 4.12.4 - 2022-04-03
• 4.12.3 - 2021-07-30
• 4.12.2 - 2021-07-19
• 4.12.1 - 2021-07-07
• 4.12.0 - 2021-07-06
• 4.11.4 - 2021-04-27
• 4.11.3 - 2021-01-24
• 4.11.3-deprecations.1 - 2021-01-25
• 4.11.3-deprecations.0 - 2021-01-24
• 4.11.2 - 2020-12-02
• 4.11.1 - 2020-11-24
• 4.11.0 - 2020-06-30
• 4.10.2 - 2020-06-11
• 4.10.1 - 2020-06-01
• 4.10.0 - 2020-05-23
• 4.9.14 - 2020-05-11
• 4.9.13 - 2020-05-04
• 4.9.12 - 2020-04-26
• 4.9.11 - 2020-04-18
• 4.9.10 - 2020-04-11
• 4.9.9 - 2020-04-04
• 4.9.8 - 2020-03-28
• 4.9.7 - 2020-03-18
• 4.9.6 - 2020-03-18
• 4.9.5 - 2020-02-29

from @material-ui/core GitHub release notes

Package name: htm

• 2.2.1 - 2019-07-31
  

  Maintenance release: adds .mjs copies of the new .module.js dist files to avoid broken unpkg links (#113).

• 2.2.0 - 2019-07-29
  
  • Adds support for namespaced JSX elements and attributes (<a:b c:d="e" />)
• 2.1.1 - 2019-02-28

from htm GitHub release notes

Package name: preact-render-to-string

• 5.2.6 - 2022-10-23
  

  Patch Changes

  • #257 8b944b2 Thanks @ marvinhagemeister! - Fix preact/debug incorrectly throwing errors on text children
• 5.2.5 - 2022-10-06
  

  Patch Changes

  • #246 ad35c4c Thanks @ developit and @ marvinhagemeister! - Fix object and function children being rendered as undefined
  • #248 aa12b3c Thanks @ marvinhagemeister! - Fix vnode masks not matching with core due to top level component Fragments
• 5.2.4 - 2022-09-10
• 5.2.3 - 2022-09-06
• 5.2.2 - 2022-08-16
  

  Patch Changes

  • #235 2f6d6e8 Thanks @ marvinhagemeister! - Remove duplicate type path in package.json. Only one of types or typings is needed.

  • 98cce12 Thanks @ JoviDeCroock! - Add types entry to package.json.

  • #228 e4fe799 Thanks @ developit! - Improve string encoding performance by ~50%
  • #229 d83def7 Thanks @ JoviDeCroock! - Split up hot paths and make separate path for opts.pretty for performance
• 5.2.1 - 2022-07-12
  

  Patch Changes

  • #224 645f3cb Thanks @ rschristian! - Ensures defaultChecked is serialized as checked attribute
  • #225 31ac323 Thanks @ JoviDeCroock! - Optimize perf by using smarter string builder

from preact-render-to-string GitHub release notes

Package name: redux

• 4.2.1 - 2023-01-28
  

  This bugfix release removes the isMinified internal check to fix a compat issue with Expo. That check has added in early 2016, soon after Redux 3.0 was released, at a time when it was still less common to use bundlers with proper production build settings. Today that check is irrelevant, so we've removed it.

  What's Changed

  • Remove minified check by @ trajano in #4454

  Full Changelog: v4.2.0...v4.2.1

• 4.2.0 - 2022-04-18
  

  This release marks the original createStore API as @ deprecated to encourage users to migrate to Redux Toolkit, and adds a new legacy_createStore API as an alias without the deprecation warning.

  Goal

  Redux Toolkit (the @ reduxjs/toolkit package) is the right way for Redux users to write Redux code today:

  https://redux.js.org/introduction/why-rtk-is-redux-today

  Unfortunately, many tutorials are still showing legacy "hand-written" Redux patterns, which result in a much worse experience for users. New learners going through a bootcamp or an outdated Udemy course just follow the examples they're being shown, don't know that RTK is the better and recommended approach, and don't even think to look at our docs.

  Given that, the goal is to provide them with a visual indicator in their editor, like createStore . When users hover over the createStore import or function call, the doc tooltip recommends using configureStore from RTK instead, and points them to that docs page. We hope that new learners will see the strikethrough, read the tooltip, read the docs page, learn about RTK, and begin using it.

  To be extremely clear:

  WE ARE NOT GOING TO ACTUALLY REMOVE THE createStore API, AND ALL YOUR EXISTING CODE WILL STILL CONTINUE TO WORK AS-IS!

  We are just marking createStore as "deprecated":

  "the discouragement of use of some feature or practice, typically because it has been superseded or is no longer considered efficient or safe, without completely removing it or prohibiting its use"

  For additional details, see the extensive discussion in #4325 .

  Rationale

  • RTK provides a vastly improved Redux usage experience, with APIs that simplify standard usage patterns and eliminate common bugs like accidental mutations
  • We've had suggestions to merge all of RTK into the redux core package, or fully deprecate the entire redux package and rename it to @ reduxjs/core. Unfortunately, those bring up too many complexities:
    • We already had a package rename from redux-starter-kit to @ reduxjs/toolkit, and all of our docs and tutorials have pointed to it for the last three years. I don't want to put users through another whiplash package transition for no real benefit
    • Merging or rearranging our packages would effectively require merging all of the Redux repos into a single monorepo. That would require hundreds of hours of effort from us maintainers, including needing to somehow merge all of our docs sites together. We don't have the time to do that.
  • I don't want to add runtime warnings that would be really annoying

  So, this is the minimum possible approach we can take to reach out to users who otherwise would never know that they are following outdated patterns, while avoiding breaking running user code or having to completely rewrite our package and repo structure.

  Results

  When a user imports createStore in their editor, they will see a visual strikethrough. Hovering over it will show a doc tooltip that encourages them to use configureStore from RTK, and points to an explanatory docs page:

  

  Again, no broken code, and no runtime warnings.

  If users do not want to see that strikethrough, they have three options:

  • Follow our suggestion to switch over to Redux Toolkit and configureStore
  • Do nothing. It's just a visual strikethrough, and it doesn't affect how your code behaves. Ignore it.
  • Switch to using the legacy_createStore API that is now exported, which is the exact same function but with no @ deprecation tag. The simplest option is to do an aliased import rename:

  

  What's Changed

  • Mark createStore as deprecated, and add legacy_createStore alias by @ markerikson in #4336

  Full Changelog: v4.1.2...v4.2.0

from redux GitHub release notes

Package name: react-redux

• 7.2.9 - 2022-09-23
  

  This patch release updates the rarely-used areStatesEqual option for connect to now pass through ownProps for additional use in determining which pieces of state to compare if desired.

  The new signature is:

  {
    areStatesEqual?: (
      nextState: State,
      prevState: State,
      nextOwnProps: TOwnProps,
      prevOwnProps: TOwnProps
    ) => boolean
  }

  What's Changed

  • connect: pass ownProps to areStatesEqual by @ jspurlin in #1952

  Full Changelog: v7.2.8...v7.2.9

• 7.2.8 - 2022-04-01
  

  This release fixes a bug in the 7.x branch that caused <Provider> to unsubscribe and stop updating completely when used inside of React 18's <StrictMode>. The new "strict effects" behavior double-mounts components, and the subscription needed to be set up inside of a useLayoutEffect instead of a useMemo. This was previously fixed as part of v8 development, and we've backported it.

  Note: If you are now using React 18, we strongly recommend using the React-Redux v8 beta instead of v7.x!. v8 has been rewritten internally to work correctly with React 18's Concurrent Rendering capabilities. React-Redux v7 will run and generally work okay with existing code, but may have rendering issues if you start using Concurrent Rendering capabilities in your code.

  Now that React 18 is out, we plan to finalize React-Redux v8 and release it live within the next couple weeks. Per an update yesterday in the "v8 roadmap" thread, React-Redux v8 will be updated in the next couple days to ensure support for React 16.8+ as part of the next beta release. We would really appreciate final feedback on using React-Redux v8 beta with React 18 before we publish the final version.

  Full Changelog: v7.2.7...v7.2.8

from react-redux GitHub release notes

Package name: react-router

• 5.3.4 - 2022-10-02
• 5.3.3 - 2022-05-18

from react-router GitHub release notes

Package name: react-router-dom

• 5.3.4 - 2022-10-02
• 5.3.3 - 2022-05-18

from react-router-dom GitHub release notes

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• This PR was automatically created by Snyk using the credentials of a real user.

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

• 🧐 View latest project report
• 📜 Customise PR templates
• 🛠 Adjust upgrade PR settings
• 🔕 Ignore this dependency or unsubscribe from future upgrade PRs

[github-actions]

Pull Request Test Coverage Report for Build 10900085357

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 98.536%

---

Totals
Change from base Build 3357135152:	0.0%
Covered Lines:	637
Relevant Lines:	640

---

💛 - Coveralls