gatsby icon indicating copy to clipboard operation
gatsby copied to clipboard

chore(deps): update [dev] major dependencies for gatsby-source-wordpress (major)

Open renovate[bot] opened this issue 3 years ago • 0 comments

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@types/cache-manager ^2.10.3 -> ^4.0.1 age adoption passing confidence
react-test-renderer (source) ^16.14.0 -> ^18.2.0 age adoption passing confidence
wait-on ^4.0.2 -> ^6.0.1 age adoption passing confidence

Release Notes

facebook/react

v18.2.0

Compare Source

React DOM
React DOM Server
Server Components (Experimental)

v18.1.0

Compare Source

React DOM
React DOM Server
ESLint Plugin: React Hooks
Use Subscription

v18.0.0

Compare Source

Below is a list of all new features, APIs, deprecations, and breaking changes. Read React 18 release post and React 18 upgrade guide for more information.

New Features
React
  • useId is a new hook for generating unique IDs on both the client and server, while avoiding hydration mismatches. It is primarily useful for component libraries integrating with accessibility APIs that require unique IDs. This solves an issue that already exists in React 17 and below, but it’s even more important in React 18 because of how the new streaming server renderer delivers HTML out-of-order.
  • startTransition and useTransition let you mark some state updates as not urgent. Other state updates are considered urgent by default. React will allow urgent state updates (for example, updating a text input) to interrupt non-urgent state updates (for example, rendering a list of search results).
  • useDeferredValue lets you defer re-rendering a non-urgent part of the tree. It is similar to debouncing, but has a few advantages compared to it. There is no fixed time delay, so React will attempt the deferred render right after the first render is reflected on the screen. The deferred render is interruptible and doesn't block user input.
  • useSyncExternalStore is a new hook that allows external stores to support concurrent reads by forcing updates to the store to be synchronous. It removes the need for useEffect when implementing subscriptions to external data sources, and is recommended for any library that integrates with state external to React.
  • useInsertionEffect is a new hook that allows CSS-in-JS libraries to address performance issues of injecting styles in render. Unless you’ve already built a CSS-in-JS library we don’t expect you to ever use this. This hook will run after the DOM is mutated, but before layout effects read the new layout. This solves an issue that already exists in React 17 and below, but is even more important in React 18 because React yields to the browser during concurrent rendering, giving it a chance to recalculate layout.
React DOM Client

These new APIs are now exported from react-dom/client:

  • createRoot: New method to create a root to render or unmount. Use it instead of ReactDOM.render. New features in React 18 don't work without it.
  • hydrateRoot: New method to hydrate a server rendered application. Use it instead of ReactDOM.hydrate in conjunction with the new React DOM Server APIs. New features in React 18 don't work without it.

Both createRoot and hydrateRoot accept a new option called onRecoverableError in case you want to be notified when React recovers from errors during rendering or hydration for logging. By default, React will use reportError, or console.error in the older browsers.

React DOM Server

These new APIs are now exported from react-dom/server and have full support for streaming Suspense on the server:

  • renderToPipeableStream: for streaming in Node environments.
  • renderToReadableStream: for modern edge runtime environments, such as Deno and Cloudflare workers.

The existing renderToString method keeps working but is discouraged.

v17.0.2

Compare Source

React DOM

v17.0.1

Compare Source

React DOM

v17.0.0

Compare Source

Today, we are releasing React 17!

Learn more about React 17 and how to update to it on the official React blog.

React
React DOM
React DOM Server
React Test Renderer
Concurrent Mode (Experimental)
jeffbski/wait-on

v6.0.1

Compare Source

Updated minor dependencies to fix vulnerabilities

v6.0.0

Compare Source

Other than dropping support for Node.js v8 there should be no other breaking changes.

Node.js v8 was no longer supported by the yargs parser. Node.js v8 users should use v5.3.0

v5.3.0

Compare Source

Allow resources to be passed in via config file. Thanks @​michaelmerrill for the PR.

Example config.js file with resources

module.exports = {
  resources: ['http://localhost:8123', 'http://localhost:8123/foo'],
};

v5.2.2

Compare Source

Updated [email protected]

Updated lodash dependency to close vulnerability

v5.2.1

Compare Source

Update dependencies

v5.2.0

Compare Source

  • expose the remaining resources in the timeout error message (thanks @​jmealo)
  • update from the deprecated @hapi/joi to joi (thanks @​AleF83)

v5.1.0

Compare Source

Add proxy option which can override the http(s) proxy which might be configured in environment variables.

  • opts.proxy: undefined, false, or object as defined in axios. Default is undefined. If not set (undefined) axios detects proxy from env vars http_proxy and https_proxy. https://github.com/axios/axios#config-defaults
  // example proxy object
  {
    host: '127.0.0.1',
    port: 9000,
    auth: {
      username: 'mikeymike',
      password: 'rapunz3l'
    }
  }

v5.0.3

Compare Source

update to [email protected]

v5.0.2

Compare Source

[email protected] update which resolved some potential lodash vulnerabilities

v5.0.1

Compare Source

Force axios to use http adapter to keep logs clean if jest/jsdom are used with the wait-on API.

If jest/jsdom is used then a polyfill for xhr is created which will cause axios to default the adapter to it. Since jsdom logs all errors use of wait-on will have any failed attempts to connect logged which is rather noisy and misleading.

By forcing axios to use the node.js http adapter instead this problem is bypassed keeping logs clean.

v5.0.0

Compare Source

Switch HTTP client from request to axios

Since the request package is no longer receiving updates, wait-on switched to using axios. Attempt to keep the same wait-on options as much as possible.

These breaking changes occurred in the switch:

  1. There is only one option for redirects followRedirect: true|false (defaults to true).
  2. httpSignature is not implemented in axios and now not available. (If this feature is still desired, please help by providing a pull request to implement it.)
  3. auth allows only username and password but not the previous aliases user and pass

add optional validateStatus fn property

If validateStatus property is provided in the config and set to a function, it will use this to validate whether a status is valid.

The default validateStatus if not provided is

validateStatus: function (status) {
  return status >= 200 && status < 300;
}

To also allow a 401 unauthorized as a valid status

validateStatus: function (status) {
  return status === 401 || (status >= 200 && status < 300);
}

Configuration

📅 Schedule: Branch creation - "before 7am on the first day of the month" in timezone GMT, Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • [ ] If you want to rebase/retry this PR, click this checkbox.

This PR has been generated by Mend Renovate. View repository job log here.

renovate[bot] avatar Aug 01 '21 03:08 renovate[bot]