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.

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

[Snyk] Upgrade: react, react-dom, http-server, prop-types, react-redux, redux, react-beautiful-dnd, react-router-dom, shortid #346

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

[Snyk] Upgrade: react, react-dom, http-server, prop-types, react-redux, redux, react-beautiful-dnd, react-router-dom, shortid #346

wants to merge 1 commit into from

Conversation

Karol-Sobolewski
Copy link
Owner

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

react
from 16.13.1 to 16.14.0 | 1 version ahead of your current version | 4 years ago
on 2020-10-14
react-dom
from 16.13.1 to 16.14.0 | 1 version ahead of your current version | 4 years ago
on 2020-10-14
http-server
from 0.12.3 to 0.13.0 | 1 version ahead of your current version | 3 years ago
on 2021-08-07
prop-types
from 15.7.2 to 15.8.1 | 2 versions ahead of your current version | 3 years ago
on 2022-01-05
react-redux
from 7.2.0 to 7.2.9 | 9 versions ahead of your current version | 2 years ago
on 2022-09-23
redux
from 4.0.5 to 4.2.1 | 7 versions ahead of your current version | 2 years ago
on 2023-01-28
react-beautiful-dnd
from 13.0.0 to 13.1.1 | 2 versions ahead of your current version | 2 years ago
on 2022-08-30
react-router-dom
from 5.0.0 to 5.3.4 | 11 versions ahead of your current version | 2 years ago
on 2022-10-02
shortid
from 2.2.15 to 2.2.16 | 1 version ahead of your current version | 4 years ago
on 2020-10-21

Issues fixed by the recommended upgrade:

Issue Score Exploit Maturity
high severity Denial of Service (DoS)
SNYK-JS-ECSTATIC-540354		 696 Proof of Concept
high severity Regular Expression Denial of Service (ReDoS)
SNYK-JS-UAPARSERJS-1023599		 696 Proof of Concept
high severity Regular Expression Denial of Service (ReDoS)
SNYK-JS-UAPARSERJS-610226		 696 Proof of Concept
medium severity Information Exposure
SNYK-JS-NODEFETCH-2342118		 696 No Known Exploit
medium severity Denial of Service
SNYK-JS-NODEFETCH-674311		 696 No Known Exploit
medium severity Regular Expression Denial of Service (ReDoS)
SNYK-JS-UAPARSERJS-1072471		 696 Proof of Concept
Release notes
Package name: react from react GitHub release notes
Package name: react-dom from react-dom GitHub release notes
Package name: http-server
  • 0.13.0 - 2021-08-07

    A long time coming, the next major release for http-server! This will be the final release before a switch to actual semantic versioning. This release's major achievement is the internalization of the functionality of the now-abandoned ecstatic library, thus removing it as a dependency. Huge thanks to @ zbynek for help on that front, as well as several other included changes.

    Breaking changes:

    • No longer sends the header server: http-server-${version} with every response

    New features:

    • All responses include Accept-Ranges: bytes to advertise support for partial requests

    Fixes

    • Removes dependency on the abandoned ecstatic library
    • Dependency upgrades to fix several security alerts
    • http-server -a 0.0.0.0 will now do what you told it to do, rather than overriding the address to 127.0.0.1
    • Will no longer serve binary files with a charset in the Content-Type, fixing serving WebAssembly files, among other issues
    • Support .mjs MimeType correctly

    Internal

    • Switched from Travis to GH Actions for CI
  • 0.12.3 - 2020-04-27

    Patch release to package man page

from http-server GitHub release notes
Package name: prop-types
  • 15.8.1 - 2022-01-05
    • [Fix] fix crash when a custom propType return lacks .data; call hasOwnProperty properly (#370)
    • [meta] Fix formatting in CHANGELOG.md (#367)
    • [Tests] add missing test coverage (#370)
    • [Tests] convert normal it functions to arrow functions (#370)
    • [Tests] do not fail fast; add react 17 (#366)
    • [Dev Deps] update eslint
  • 15.8.0 - 2021-12-22
    • [New] add PropTypes.bigint (#365)
    • [New] oneOfType: Add expected types to warning (#198)
    • [New] Add type check for validator for 'shape' and 'exact' (#234)
    • [Fix] checkPropTypes: Friendlier message when using a type checker that is not a function (#51)
    • [Refactor] extract has (#261, #125, #124)
    • [readme] Fix branch name (master -> main) (#364)
    • [readme] Clarify usage of elementType (#335)
    • [docs] highlighted the func name (#321)
    • [docs] Typo fix in example (#300)
    • [docs] Add instructions for intentional inclusion of validation in production. (#262)
    • [docs] PropTypes.node: add link to react docs
    • [docs] Improve wording for checkPropTypes (#258)
    • [meta] Add a package sideEffects field. (#350)
    • [meta] use in-publish to avoid running the build on install
    • [deps] regenerate yarn.lock
    • [deps] update react-is (#347, #346, #345, #340, #338)
    • [eslint] enable some rules (#360)
    • [Tests] Use GH Actions (#363)
    • [Tests] Fix spelling (#318)
    • [Tests] Fixed typo: 'Any type should accept any value' (#281)
    • [Tests] fix broken tests; test the build process
    • [Dev Deps] update browserify, bundle-collapser, eslint, in-publish, react, uglifyify, uglifyjs
  • 15.7.2 - 2019-02-13

    v15.7.2

from prop-types 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
  • 7.2.3 - 2021-03-23
  • 7.2.2 - 2020-10-26
  • 7.2.1 - 2020-07-25
  • 7.2.0 - 2020-02-18
from react-redux 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
  • 4.1.0-alpha.0 - 2021-04-04

    This pre-release for 4.1.0 shrinks our bundle size via tooling updates, and updates several error messages for clarity. This is all the changes we plan to have for 4.1, so if feedback looks good, we'll release 4.1.0 shortly.

    Changelog Summary

    The 4.1.0 release will have a more complete changelog, but summarizing:

    • Shrinks our bundle sizes by extracting error messages from production builds and replacing them with error codes (similar to React). Thanks to @ andrewmcgivery for implementing this!
    • Inlines the symbol-observable polyfill
    • Drops the legacy loose-envify dependency
    • Externalizes the @ babel/runtime helpers
    • Fixed a TS typedef to work better with TS 4.3

    We've also updated the error messages to clarify what's happening, provide more details when runtime type checks fail, and link to relevant documentation.

    Changes

    • Merge pull request #4058 from reduxjs/feature/4x-remove-legacy-deps 9a1d065
    • Inline the symbol-observable polyfill 0d7d94d
    • Remove symbol-observable and loose-envify deps b882d9a
    • Merge pull request #4057 from reduxjs/feature/4x-error-messages f3680b5
    • Port error message updates from master 46f5c94
    • Port error extraction setup from master 05d5505
    • Merge pull request #4056 from reduxjs/feature/4x-update-build-tooling 82ad636
    • fix: Declare "EmptyObject" interface to wrap $CombinedState (#4031) c3cbe2e
    • Only apply mapped types to un-branded types (#3805) e23aa59

    v4.0.5...v4.1.0-alpha.0

  • 4.0.5 - 2019-12-24

    This release includes a memory leak fix, and a fix for removing reducers with replaceReducer and combineReducers.

    There are also some TypeScript changes, which require version 3.5 or higher. This also removes our DeepPartial type, which wasn't intended to be a public API. If you need this type, you can find an equivalent of likely higher quality in the utility-types package.

    Speaking of TypeScript, we are done with converting the code to TypeScript on master and are looking to get some TS improvements in before launching 5.0. If you're interested in helping, feel free to submit a PR with anything you'd like to contribute.

    Changes

from redux GitHub release notes
Package name: react-beautiful-dnd
  • 13.1.1 - 2022-08-30
    • Adds react v18 to the list of supported react versions via peerDependency.
    • Various dependency bumps
    • Various changes to documentation
  • 13.1.0 - 2021-03-21

    Features

    You can now import default sensors as useMouseSensor, useKeyboardSensor, or useTouchSensor for individual reuse via sensors prop
    – Thanks @ vladmoroz

    React 17 is now supported 🎉
    – Thanks @ 100terres

    Fixes

    Removed redundant event listener
    – Thanks @ hodovani

    Misc

    Various improvements to the docs and examples
    – Thanks @ theBstar @ Ardeshir81 @ hednowley @ RavenAlly @ alexbudure @ vkentta @ johnrees @ agilatakishiyev @ petyosi @ inokawa @ ToriK17 @ paulshen @ ValentinH @ featherbear @ GarrisonJ

    Documentation is now available in Greek 🇬🇷
    – Thanks @ hdks55l

    Story source code is now visible in Storybook
    – Thanks @ 2stash

    Various internal changes
    – Thanks @ ValentinH

  • 13.0.0 - 2020-02-24

    release banner image

    📷 Cover photo by Matheus Ferrero on Unsplash

    🎧 Release soundtrack: Colder Heavens - Blanco White

    Highlights

    • 🛠 Babel changes: no more unintentional polyfilling!
    • ♿️ More reliable on focus messaging. Verified on VoiceOver, JAWS and NVDA screen readers

    This is a low risk breaking version. It is essentially a bug fix release with some API changes. You might need to make some changes if you were unintentionally relying on our unexpected polyfilling, or if you are overriding our default screen reader messaging, then there will be some stuff for you to do.

    Babel

    This has been marked this as a breaking change 💥 as consumers might have been unknowingly relying on polyfills in rbd as a side effect 😲. This is a very low risk breaking change

    We have moved from @ babel/runtime-corejs2 to @ babel/runtime

@snyk-bot
fix: upgrade multiple dependencies with Snyk
caf1b0f 
Snyk has created this PR to upgrade:
  - react from 16.13.1 to 16.14.0.
    See this package in npm: https://www.npmjs.com/package/react
  - react-dom from 16.13.1 to 16.14.0.
    See this package in npm: https://www.npmjs.com/package/react-dom
  - http-server from 0.12.3 to 0.13.0.
    See this package in npm: https://www.npmjs.com/package/http-server
  - prop-types from 15.7.2 to 15.8.1.
    See this package in npm: https://www.npmjs.com/package/prop-types
  - react-redux from 7.2.0 to 7.2.9.
    See this package in npm: https://www.npmjs.com/package/react-redux
  - redux from 4.0.5 to 4.2.1.
    See this package in npm: https://www.npmjs.com/package/redux
  - react-beautiful-dnd from 13.0.0 to 13.1.1.
    See this package in npm: https://www.npmjs.com/package/react-beautiful-dnd
  - react-router-dom from 5.0.0 to 5.3.4.
    See this package in npm: https://www.npmjs.com/package/react-router-dom
  - shortid from 2.2.15 to 2.2.16.
    See this package in npm: https://www.npmjs.com/package/shortid

See this project in Snyk:
https://app.snyk.io/org/karol-sobolewski/project/4589bdb2-303c-4ad5-99e9-bdd63f2a50e6?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.
2 participants
@Karol-Sobolewski @snyk-bot