Skip to content

[Snyk] Upgrade: core-js, redux, react-redux, typescript #3

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.

Sign up for GitHub

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

Jump to bottom
Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

[Snyk] Upgrade: core-js, redux, react-redux, typescript #3

wants to merge 1 commit into from

Conversation

@xiezhifeng
Copy link
Owner

@xiezhifeng xiezhifeng commented Sep 22, 2024

snyk-top-banner

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

core-js
from 3.12.1 to 3.38.1 | 81 versions ahead of your current version | a month ago
on 2024-08-20
redux
from 4.1.0 to 4.2.1 | 5 versions ahead of your current version | 2 years ago
on 2023-01-28
react-redux
from 7.2.4 to 7.2.9 | 5 versions ahead of your current version | 2 years ago
on 2022-09-23
typescript
from 4.2.4 to 4.9.5 | 634 versions ahead of your current version | 2 years ago
on 2023-01-30

Release notes
Package name: core-js from core-js 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

    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:

    image

    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:

    image

    What's Changed

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

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

  • 4.2.0-alpha.0 - 2021-10-30

    4.2.0-alpha.0

  • 4.1.2 - 2021-10-28

    This release fixes a small specific TS types issue where state types that had a nested unknown field inside would cause compilation failures when used as the preloadedState argument.

    What's Changed

    Full Changelog: v4.1.1...v4.1.2

  • 4.1.1 - 2021-08-03

    Just a small fix for Safari users in development mode.

    Changes

    • Move miniKindOf out of if scope to fix ES5 compatibility issue (#4090 by @ embeddedt)
  • 4.1.0 - 2021-04-24

    This release shrinks our bundle size via error message extraction, updates several error messages for clarity, and optimizes our list of runtime dependencies.

    Overall, version 4.1 shrinks from 2.6K min+gz to 1.6K min+gz thanks to these changes.

    Be sure to check out the Redux Toolkit 1.6 alpha containing our new "RTK Query" data fetching APIs! It also includes Redux 4.1 as a dependency.

    Changelog

    Error Message Extraction and Improvements

    We now extract all of our error messages from production builds in order to save on bundle size, using a technique inspired from React's error code extraction. The error messages will still show as normal in development, but in production they will reference a specific numeric error code and provide a link to a Redux docs page that has the full error message.

    An example of this is: https://redux.js.org/errors?code=5 , which shows the "can't subscribe while reducers are executing" error.

    The error code extraction saves about 800 bytes out of a production build.

    Thanks to @ andrewmcgivery for doing all the hard work on implementing the error extraction!

    We've also updated many of our error messages to provide additional details at runtime about what happened, especially runtime type checks such as "actions must be plain objects". They now provide a more specific type for the unexpected value, such as indicating promise or function:

    Changes
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

    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

  • 7.2.7 - 2022-03-31

    This release updates React-Redux v7's peer dependencies to accept React 18 as a valid version, only to avoid installation errors caused by NPM's "install all the peer deps and error if they don't match" behavior.

    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. We would really appreciate final feedback on using React-Redux v8 beta with React 18 before we publish the final version.

  • 7.2.6 - 2021-10-25
  • 7.2.5 - 2021-09-04
  • 7.2.4 - 2021-04-24
from react-redux GitHub release notes
Package name: typescript
  • 4.9.5 - 2023-01-30
  • 4.9.4 - 2022-12-07
  • 4.9.3 - 2022-11-15
  • 4.9.2-rc - 2022-11-01
  • 4.9.1-beta - 2022-09-23
  • 4.9.0-dev.20221031 - 2022-10-31
  • 4.9.0-dev.20221030 - 2022-10-30
  • 4.9.0-dev.20221029 - 2022-10-29
  • 4.9.0-dev.20221028 - 2022-10-28
  • 4.9.0-dev.20221027 - 2022-10-27
  • 4.9.0-dev.20221026 - 2022-10-26
  • 4.9.0-dev.20221025 - 2022-10-25
  • 4.9.0-dev.20221024 - 2022-10-24
  • 4.9.0-dev.20221023 - 2022-10-23
  • 4.9.0-dev.20221022 - 2022-10-22
  • 4.9.0-dev.20221021 - 2022-10-21
  • 4.9.0-dev.20221020 - 2022-10-20
  • 4.9.0-dev.20221019 - 2022-10-19
  • 4.9.0-dev.20221018 - 2022-10-18
  • 4.9.0-dev.20221017 - 2022-10-17
  • 4.9.0-dev.20221016 - 2022-10-16
  • 4.9.0-dev.20221015 - 2022-10-15
  • 4.9.0-dev.20221014 - 2022-10-14
  • 4.9.0-dev.20221013 - 2022-10-13
  • 4.9.0-dev.20221012 - 2022-10-12
  • 4.9.0-dev.20221011 - 2022-10-11
  • 4.9.0-dev.20221007 - 2022-10-07
  • 4.9.0-dev.20221006 - 2022-10-06
  • 4.9.0-dev.20221005 - 2022-10-05
  • 4.9.0-dev.20221004 - 2022-10-04
  • 4.9.0-dev.20221003 - 2022-10-03
  • 4.9.0-dev.20221002 - 2022-10-02
  • 4.9.0-dev.20221001 - 2022-10-01
  • 4.9.0-dev.20220930 - 2022-09-30
  • 4.9.0-dev.20220929 - 2022-09-29
  • 4.9.0-dev.20220928 - 2022-09-28
  • 4.9.0-dev.20220927 - 2022-09-27
  • 4.9.0-dev.20220926 - 2022-09-26
  • 4.9.0-dev.20220925 - 2022-09-25
  • 4.9.0-dev.20220924 - 2022-09-24
  • 4.9.0-dev.20220923 - 2022-09-23
  • 4.9.0-dev.20220922 - 2022-09-22
  • 4.9.0-dev.20220921 - 2022-09-21
  • 4.9.0-dev.20220920 - 2022-09-20
  • 4.9.0-dev.20220919 - 2022-09-19
  • 4.9.0-dev.20220918 - 2022-09-18
  • 4.9.0-dev.20220917 - 2022-09-17
  • 4.9.0-dev.20220916 - 2022-09-16
  • 4.9.0-dev.20220915 - 2022-09-15
  • 4.9.0-dev.20220914 - 2022-09-14
  • 4.9.0-dev.202209...

@snyk-bot
fix: upgrade multiple dependencies with Snyk
5a8d16e 
Snyk has created this PR to upgrade:
  - core-js from 3.12.1 to 3.38.1.
    See this package in npm: https://www.npmjs.com/package/core-js
  - redux from 4.1.0 to 4.2.1.
    See this package in npm: https://www.npmjs.com/package/redux
  - react-redux from 7.2.4 to 7.2.9.
    See this package in npm: https://www.npmjs.com/package/react-redux
  - typescript from 4.2.4 to 4.9.5.
    See this package in npm: https://www.npmjs.com/package/typescript

See this project in Snyk:
https://app.snyk.io/org/xiezhifeng/project/5808a9d1-b060-4e8e-bb98-0ed46a2b12dd?utm_source=github&utm_medium=referral&page=upgrade-pr
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@xiezhifeng @snyk-bot