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

chore(deps): update dependency react-transition-group to v4 #134

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Apr 16, 2019

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
react-transition-group 2.7.0 -> 4.4.5 age adoption passing confidence

Release Notes

reactjs/react-transition-group (react-transition-group)

v4.4.5

Compare Source

Bug Fixes
  • apply entering animation synchronously when unmountOnExit or mountOnEnter is enabled (#​847) (1043549)

v4.4.4

Compare Source

Bug Fixes

v4.4.3

Compare Source

Bug Fixes
  • enter animations with mountOnEnter or unmountOnExit (#​749) (51bdceb)

v4.4.2

Compare Source

Bug Fixes

v4.4.1

Compare Source

Bug Fixes

v4.4.0

Compare Source

Features
  • add nodeRef alternative instead of internal findDOMNode (#​559) (85016bf)
    • react-transition-group internally uses findDOMNode, which is deprecated and produces warnings in Strict Mode, so now you can optionally pass nodeRef to Transition and CSSTransition, it's a ref object that should point to the transitioning child:

      import React from "react"
      import { CSSTransition } from "react-transition-group"
      
      const MyComponent = () => {
        const nodeRef = React.useRef(null)
        return (
          <CSSTransition nodeRef={nodeRef} in timeout={200} classNames="fade">
            <div ref={nodeRef}>Fade</div>
          </CSSTransition>
        )
      }
Bug Fixes
  • set the values of constants attached to Transition to match the exported ones (#​554)

v4.3.0

Compare Source

Features

4.2.2 (2019-08-02)

Bug Fixes

4.2.1 (2019-07-02)

Bug Fixes
  • updated SwitchTransition component to be default export and exported from index.js (#​516) (cfd0070)

v4.2.2

Compare Source

Bug Fixes

v4.2.1

Compare Source

Bug Fixes
  • updated SwitchTransition component to be default export and exported from index.js (#​516) (cfd0070)

v4.2.0

Compare Source

Features

4.1.1 (2019-06-10)

Bug Fixes

v4.1.1

Compare Source

Bug Fixes

v4.1.0

Compare Source

Features

4.0.1 (2019-05-09)

Bug Fixes
  • issue with dynamically applied classes not being properly removed for reentering items (#​499) (129cb11)

v4.0.1

Compare Source

Bug Fixes
  • issue with dynamically applied classes not being properly removed for reentering items (#​499) (129cb11)

v4.0.0

Compare Source

Features
BREAKING CHANGES
  • in environments where esm is supported importing from commonjs requires explicitly adding the .default after require() when resolving to the esm build

v3.0.0

Compare Source

Features
BREAKING CHANGES
  • use new style react context
// package.json
-"react": "^15.0.0",
+"react": "^16.6.0",
-"react-dom": "^15.0.0", 
+"react-dom": "^16.6.0", 

v2.9.0

Compare Source

Features
Reverts
  • bump semantic release dependencies (1bdcaec)

v2.8.0

Compare Source

Features

2.7.1 (2019-03-25)

Bug Fixes
  • revert tree-shaking support because it was a breaking change (271364c)

v2.7.1

Compare Source

Bug Fixes
  • revert tree-shaking support because it was a breaking change (271364c)

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 is behind base branch, 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 renovate bot force-pushed the renovate/react-transition-group-4.x branch from c394379 to 9fc56b1 Compare May 9, 2019 20:09
@renovate renovate bot force-pushed the renovate/react-transition-group-4.x branch from 9fc56b1 to 52ce368 Compare June 1, 2019 09:51
@renovate renovate bot force-pushed the renovate/react-transition-group-4.x branch from 52ce368 to 0ee9d65 Compare July 13, 2019 11:58
@renovate renovate bot force-pushed the renovate/react-transition-group-4.x branch from 0ee9d65 to d145325 Compare August 10, 2019 09:00
@renovate renovate bot force-pushed the renovate/react-transition-group-4.x branch from d145325 to 2c3f4bd Compare September 7, 2019 16:57
@renovate renovate bot force-pushed the renovate/react-transition-group-4.x branch from 2c3f4bd to bdfe367 Compare July 1, 2020 11:51
@renovate renovate bot changed the title feat(deps): update dependency react-transition-group to v4 chore(deps): update dependency react-transition-group to v4 Jan 5, 2021
@renovate renovate bot force-pushed the renovate/react-transition-group-4.x branch from bdfe367 to de3701e Compare June 6, 2021 21:24
@renovate
Copy link
Contributor Author

renovate bot commented Jun 6, 2021

⚠ 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
No /opt/buildpack/tools/node/6.9.5/bin/npx defined - aborting
npm WARN deprecated core-js@1.2.7: core-js@<3.23.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js.
npm WARN deprecated babel-eslint@8.2.2: babel-eslint is now @babel/eslint-parser. This package will no longer receive updates.
npm WARN deprecated circular-json@0.3.3: CircularJSON is in maintenance only, flatted is its successor.
npm WARN deprecated querystring@0.2.0: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
npm WARN deprecated uuid@3.2.1: Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
npm WARN deprecated core-js@2.6.12: core-js@<3.23.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js.
npm WARN deprecated html-webpack-plugin@3.0.6: out of support
npm WARN deprecated extract-text-webpack-plugin@3.0.2: Deprecated. Please use https://github.com/webpack-contrib/mini-css-extract-plugin
npm WARN deprecated eslint-loader@2.0.0: This loader has been deprecated. Please use eslint-webpack-plugin
npm WARN deprecated postcss-cssnext@3.1.0: 'postcss-cssnext' has been deprecated in favor of 'postcss-preset-env'. Read more at https://moox.io/blog/deprecating-cssnext/
npm WARN deprecated browserslist@2.11.3: Browserslist 2 could fail on reading Browserslist >3.0 config used in other tools.
npm WARN deprecated browserslist@1.7.7: Browserslist 2 could fail on reading Browserslist >3.0 config used in other tools.
npm WARN deprecated flatten@1.0.3: flatten is deprecated in favor of utility frameworks such as lodash.
npm WARN deprecated svgo@0.7.2: This SVGO version is no longer supported. Upgrade to v2.x.x.
npm WARN deprecated svgo@1.3.2: This SVGO version is no longer supported. Upgrade to v2.x.x.
npm WARN deprecated stable@0.1.8: Modern JS already guarantees Array#sort() is a stable sort, so this library is deprecated. See the compatibility table on MDN: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/sort#browser_compatibility
npm WARN deprecated chokidar@1.7.0: Chokidar 2 will break on node v14+. Upgrade to chokidar 3 with 15x less dependencies.
npm WARN deprecated source-map-resolve@0.5.3: See https://github.com/lydell/source-map-resolve#deprecated
npm WARN deprecated source-map-url@0.4.1: See https://github.com/lydell/source-map-url#deprecated
npm WARN deprecated urix@0.1.0: Please see https://github.com/lydell/urix#deprecated
npm WARN deprecated resolve-url@0.2.1: https://github.com/lydell/resolve-url#deprecated
npm WARN deprecated request@2.79.0: request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated tar@2.2.2: This version of tar is no longer supported, and will not receive security updates. Please upgrade asap.
npm WARN deprecated uuid@3.4.0: Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
npm WARN deprecated har-validator@5.1.5: this library is no longer supported
npm WARN deprecated har-validator@2.0.6: this library is no longer supported
npm WARN deprecated hawk@3.1.3: This module moved to @hapi/hawk. Please make sure to switch over as this distribution is no longer supported and may contain bugs and critical security issues.
npm WARN deprecated sntp@1.0.9: This module moved to @hapi/sntp. Please make sure to switch over as this distribution is no longer supported and may contain bugs and critical security issues.
npm WARN deprecated cryptiles@2.0.5: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
npm WARN deprecated boom@2.10.1: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
npm WARN deprecated hoek@2.16.3: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
npm WARN deprecated uglify-es@3.3.9: support for ECMAScript is superseded by `uglify-js` as of v3.13.0
npm WARN deprecated acorn-dynamic-import@2.0.2: This is probably built in to whatever tool you're using. If you still need it... idk
npm WARN deprecated chokidar@2.1.8: Chokidar 2 does not receive security updates since 2019. Upgrade to chokidar 3 with 15x fewer dependencies
npm WARN deprecated bfj-node4@5.3.1: Switch to the `bfj` package for fixes and new features!
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.0.0 (node_modules/chokidar/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.13: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@~2.3.2 (node_modules/watchpack/node_modules/chokidar/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.3.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.2.7 (node_modules/watchpack-chokidar2/node_modules/chokidar/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.13: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.2.7 (node_modules/webpack-dev-server/node_modules/chokidar/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.13: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm WARN focus-components@2.3.0-beta4 requires a peer of focus-core@>= 2.2.0 < 2.3 but none was installed.
npm WARN focus-components@2.3.0-beta4 requires a peer of react-transition-group@^2.2.1 but none was installed.
npm WARN ajv-keywords@3.5.2 requires a peer of ajv@^6.9.1 but none was installed.
npm WARN fork-ts-checker-webpack-plugin@0.4.1 requires a peer of tslint@^4.0.0 || ^5.0.0 but none was installed.
npm WARN fork-ts-checker-webpack-plugin@0.4.1 requires a peer of typescript@^2.1.0 but none was installed.
npm WARN update-browserslist-db@1.0.10 requires a peer of browserslist@>= 4.21.0 but none was installed.
npm ERR! Linux 5.4.0-1084-aws
npm ERR! argv "/opt/buildpack/tools/node/6.9.5/bin/node" "/usr/local/bin/npm" "install" "--package-lock-only" "--no-audit" "--ignore-scripts"
npm ERR! node v6.9.5
npm ERR! npm  v3.10.10
npm ERR! path /mnt/renovate/gh/FightForSub/ffs-zera/node_modules/.staging/@types/node-335ab801/package.json
npm ERR! code ENOTDIR
npm ERR! errno -20
npm ERR! syscall open

npm ERR! ENOTDIR: not a directory, open '/mnt/renovate/gh/FightForSub/ffs-zera/node_modules/.staging/@types/node-335ab801/package.json'
npm ERR! 
npm ERR! If you need help, you may report this error at:
npm ERR!     <https://github.com/npm/npm/issues>

npm ERR! Please include the following file with any support request:
npm ERR!     /mnt/renovate/gh/FightForSub/ffs-zera/npm-debug.log

@renovate renovate bot force-pushed the renovate/react-transition-group-4.x branch from de3701e to 4e34951 Compare November 20, 2022 08:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant