kjuulh/vidow
1
0
Fork 0
Code Issues 1 Pull Requests 4 Packages Projects Releases Wiki Activity

Update all dependencies #119

Merged
kjuulh merged 1 commits from renovate/all into main 2023-06-19 15:48:40 +02:00
Conversation 0 Commits 1 Files Changed 4 +23 -23
kjuulh commented 2023-05-21 23:23:13 +02:00
Owner
Copy Link

This PR contains the following updates:

Package Type Update Change
@types/node (source) devDependencies patch 18.16.13 -> 18.16.18
clap dependencies patch 4.3.0 -> 4.3.4
react-redux dependencies minor 8.0.5 -> 8.1.0
typescript (source) devDependencies minor 5.0.4 -> 5.1.3

Release Notes

clap-rs/clap

v4.3.4

Compare Source

Features
  • Add Error::exit_code

v4.3.3

Compare Source

Features
  • Command::defer for delayed initialization of subcommands to reduce startup times of large applications like deno

v4.3.2

Compare Source

Fixes
  • (derive) Don't produce unused_equalifications warnings when someone brings a clap type into scope

v4.3.1

Compare Source

Performance
  • (derive) Reduce the amount of generated code
reduxjs/react-redux

v8.1.0

Compare Source

This feature release adds new development-mode safety checks for common errors (like poorly-written selectors), adds a workaround to fix crash errors when React-Redux hooks are imported into React Server Component files, and updates our hooks API docs page with improved explanations and updated links.

Changelog

Development Mode Checks for useSelector

We've had a number of users tell us over time that it's common to accidentally write selectors that have bad behavior and cause performance issues. The most common causes of this are either selectors that unconditionally return a new reference (such as state => state.todos.map() without any memoization ), or selectors that actually return the entire root state ( state => state ).

We've updated useSelector to add safety checks in development mode that warn if these incorrect behaviors are detected:

  • Selectors will be called twice with the same inputs, and useSelector will warn if the results are different references
  • useSelector will warn if the selector result is actually the entire root state

By default, these checks only run once the first time useSelector is called. This should provide a good balance between detecting possible issues, and keeping development mode execution performant without adding many unnecessary extra selector calls.

If you want, you can configure this behavior globally by passing the enum flags directly to <Provider>, or on a per-useSelector basis by passing an options object as the second argument:

// Example: globally configure the root state "noop" check to run every time
<Provider store={store} noopCheck="always">
  {children}
</Provider>

// Example: configure `useSelector` to specifically run the reference checks differently:
function Component() {
  // Disable check entirely for this selector
  const count = useSelector(selectCount, { stabilityCheck: 'never' })
  // run once (default)
  const user = useSelector(selectUser, { stabilityCheck: 'once' })
  // ...
}

This goes along with the similar safety checks we've added to Reselect v5 alpha as well.

Context Changes

We're still trying to work out how to properly use Redux and React Server Components together. One possibility is using RTK Query's createApi to define data fetching endpoints, and using the generated thunks to fetch data in RSCs, but it's still an open question.

However, users have reported that merely importing any React-Redux API in an RSC file causes a crash, because React.createContext is not defined in RSC files. RTKQ's React-specific createApi entry point imports React-Redux, so it's been unusable in RSCs.

This release adds a workaround to fix that issue, by using a proxy wrapper around our singleton ReactReduxContext instance and lazily creating that instance on demand. In testing, this appears to both continue to work in all unit tests, and fixes the import error in an RSC environment. We'd appreciate further feedback in case this change does cause any issues for anyone!

We've also tweaked the internals of the hooks to do checks for correct <Provider> usage when using a custom context, same as the default context checks.

Docs Updates

We've cleaned up some of the Hooks API reference page, and updated links to the React docs.

What's Changed

Full Changelog: https://github.com/reduxjs/react-redux/compare/v8.0.7...v8.1.0

v8.0.7

Compare Source

This release updates the peer dependencies to accept Redux Toolkit, and accept the ongoing RTK and Redux core betas as valid peer deps.

Note

: These changes were initially in 8.0.6, but that had a typo in the peer deps that broke installation. Sorry!

What's Changed

Full Changelog: https://github.com/reduxjs/react-redux/compare/v8.0.5...v8.0.7

v8.0.6

Compare Source

~~This release updates the peer dependencies to accept Redux Toolkit, and accept the ongoing RTK and Redux core betas as valid peer deps.~~

This release has a peer deps typo that breaks installation - please use 8.0.7 instead !

What's Changed

Full Changelog: https://github.com/reduxjs/react-redux/compare/v8.0.5...v8.0.6

Microsoft/TypeScript

v5.1.3: TypeScript 5.1.3

Compare Source

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

Downloads are available on:

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), 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, check this box

This PR has been generated by Renovate Bot.

This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | [@types/node](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/node) ([source](https://github.com/DefinitelyTyped/DefinitelyTyped)) | devDependencies | patch | [`18.16.13` -> `18.16.18`](https://renovatebot.com/diffs/npm/@types%2fnode/18.16.13/18.16.18) | | [clap](https://github.com/clap-rs/clap) | dependencies | patch | `4.3.0` -> `4.3.4` | | [react-redux](https://github.com/reduxjs/react-redux) | dependencies | minor | [`8.0.5` -> `8.1.0`](https://renovatebot.com/diffs/npm/react-redux/8.0.5/8.1.0) | | [typescript](https://www.typescriptlang.org/) ([source](https://github.com/Microsoft/TypeScript)) | devDependencies | minor | [`5.0.4` -> `5.1.3`](https://renovatebot.com/diffs/npm/typescript/5.0.4/5.1.3) | --- ### Release Notes <details> <summary>clap-rs/clap</summary> ### [`v4.3.4`](https://github.com/clap-rs/clap/blob/HEAD/CHANGELOG.md#&#8203;434---2023-06-14) [Compare Source](https://github.com/clap-rs/clap/compare/v4.3.3...v4.3.4) ##### Features - Add `Error::exit_code` ### [`v4.3.3`](https://github.com/clap-rs/clap/blob/HEAD/CHANGELOG.md#&#8203;433---2023-06-09) [Compare Source](https://github.com/clap-rs/clap/compare/v4.3.2...v4.3.3) ##### Features - `Command::defer` for delayed initialization of subcommands to reduce startup times of large applications like deno ### [`v4.3.2`](https://github.com/clap-rs/clap/blob/HEAD/CHANGELOG.md#&#8203;432---2023-06-05) [Compare Source](https://github.com/clap-rs/clap/compare/v4.3.1...v4.3.2) ##### Fixes - *(derive)* Don't produce `unused_equalifications` warnings when someone brings a clap type into scope ### [`v4.3.1`](https://github.com/clap-rs/clap/blob/HEAD/CHANGELOG.md#&#8203;431---2023-06-02) [Compare Source](https://github.com/clap-rs/clap/compare/v4.3.0...v4.3.1) ##### Performance - *(derive)* Reduce the amount of generated code </details> <details> <summary>reduxjs/react-redux</summary> ### [`v8.1.0`](https://github.com/reduxjs/react-redux/releases/tag/v8.1.0) [Compare Source](https://github.com/reduxjs/react-redux/compare/v8.0.7...v8.1.0) This **feature release** adds new development-mode safety checks for common errors (like poorly-written selectors), adds a workaround to fix crash errors when React-Redux hooks are imported into React Server Component files, and updates our hooks API docs page with improved explanations and updated links. #### Changelog ##### Development Mode Checks for `useSelector` We've had a number of users tell us over time that it's common to accidentally write selectors that have bad behavior and cause performance issues. The most common causes of this are either selectors that unconditionally return a new reference (such as `state => state.todos.map()` without any memoization ), or selectors that actually return the *entire* root state ( `state => state` ). We've updated `useSelector` to add safety checks in development mode that warn if these incorrect behaviors are detected: - Selectors will be called twice with the same inputs, and `useSelector` will warn if the results are different references - `useSelector` will warn if the selector result is actually the entire root `state` By default, **these checks only run *once* the first time `useSelector` is called**. This should provide a good balance between detecting possible issues, and keeping development mode execution performant without adding many unnecessary extra selector calls. If you want, you can configure this behavior globally by passing the enum flags directly to `<Provider>`, or on a per-`useSelector` basis by passing an options object as the second argument: ```ts // Example: globally configure the root state "noop" check to run every time <Provider store={store} noopCheck="always"> {children} </Provider> ``` ```ts // Example: configure `useSelector` to specifically run the reference checks differently: function Component() { // Disable check entirely for this selector const count = useSelector(selectCount, { stabilityCheck: 'never' }) // run once (default) const user = useSelector(selectUser, { stabilityCheck: 'once' }) // ... } ``` This goes along with the similar safety checks we've added to [Reselect v5 alpha](https://github.com/reduxjs/reselect/releases/tag/v5.0.0-alpha.2) as well. ##### Context Changes We're still trying to work out how to properly use Redux and React Server Components together. One possibility is using RTK Query's `createApi` to define data fetching endpoints, and using the generated thunks to fetch data in RSCs, but it's still an open question. However, users have reported that merely importing *any* React-Redux API in an RSC file causes a crash, because `React.createContext` is not defined in RSC files. RTKQ's React-specific `createApi` entry point imports React-Redux, so it's been unusable in RSCs. This release adds a workaround to fix that issue, by using a proxy wrapper around our singleton `ReactReduxContext` instance and lazily creating that instance on demand. In testing, this appears to both continue to work in all unit tests, *and* fixes the import error in an RSC environment. We'd appreciate further feedback in case this change does cause any issues for anyone! We've also tweaked the internals of the hooks to do checks for correct `<Provider>` usage when using a custom context, same as the default context checks. ##### Docs Updates We've cleaned up some of the Hooks API reference page, and updated links to the React docs. #### What's Changed - check for Provider even when using custom context by [@&#8203;EskiMojo14](https://github.com/EskiMojo14) in https://github.com/reduxjs/react-redux/pull/1990 - Add a stability check, to see if selector returns stable result when called with same parameters. by [@&#8203;EskiMojo14](https://github.com/EskiMojo14) in https://github.com/reduxjs/react-redux/pull/2000 - Add an E2E-ish test that verifies behavior when imported into RSCs by [@&#8203;markerikson](https://github.com/markerikson) in https://github.com/reduxjs/react-redux/pull/2030 - lazily create Context for RSC compat by [@&#8203;phryneas](https://github.com/phryneas) in https://github.com/reduxjs/react-redux/pull/2025 - Add warning for selectors that return the entire state by [@&#8203;EskiMojo14](https://github.com/EskiMojo14) in https://github.com/reduxjs/react-redux/pull/2022 **Full Changelog**: https://github.com/reduxjs/react-redux/compare/v8.0.7...v8.1.0 ### [`v8.0.7`](https://github.com/reduxjs/react-redux/releases/tag/v8.0.7) [Compare Source](https://github.com/reduxjs/react-redux/compare/v8.0.6...v8.0.7) This release updates the peer dependencies to accept Redux Toolkit, and accept the ongoing RTK and Redux core betas as valid peer deps. > **Note**: These changes were initially in 8.0.6, but that had a typo in the peer deps that broke installation. Sorry! #### What's Changed - Bump Redux peer deps to accept 5.0 betas, and bump RTK dev dep by [@&#8203;markerikson](https://github.com/markerikson) in https://github.com/reduxjs/react-redux/pull/2017 - [`d45204f`](https://github.com/reduxjs/react-redux/commit/d45204f) : Fix broken RTK peer dep **Full Changelog**: https://github.com/reduxjs/react-redux/compare/v8.0.5...v8.0.7 ### [`v8.0.6`](https://github.com/reduxjs/react-redux/releases/tag/v8.0.6) [Compare Source](https://github.com/reduxjs/react-redux/compare/v8.0.5...v8.0.6) \~~This release updates the peer dependencies to accept Redux Toolkit, and accept the ongoing RTK and Redux core betas as valid peer deps.~~ **This release has a peer deps typo that breaks installation - please use 8.0.7 instead !** #### What's Changed - Bump Redux peer deps to accept 5.0 betas, and bump RTK dev dep by [@&#8203;markerikson](https://github.com/markerikson) in https://github.com/reduxjs/react-redux/pull/2017 **Full Changelog**: https://github.com/reduxjs/react-redux/compare/v8.0.5...v8.0.6 </details> <details> <summary>Microsoft/TypeScript</summary> ### [`v5.1.3`](https://github.com/microsoft/TypeScript/releases/tag/v5.1.3): TypeScript 5.1.3 [Compare Source](https://github.com/Microsoft/TypeScript/compare/v5.0.4...v5.1.3) For release notes, check out the [release announcement](https://devblogs.microsoft.com/typescript/announcing-typescript-5-1/). For the complete list of fixed issues, check out the - [fixed issues query for Typescript 5.1.0 (Beta)](https://github.com/Microsoft/TypeScript/issues?utf8=%E2%9C%93\&q=milestone%3A%22TypeScript+5.1.0%22+is%3Aclosed+). - [fixed issues query for Typescript 5.1.1 (RC)](https://github.com/Microsoft/TypeScript/issues?utf8=%E2%9C%93\&q=milestone%3A%22TypeScript+5.1.1%22+is%3Aclosed+). - [fixed issues query for Typescript 5.1.3 (Stable)](https://github.com/Microsoft/TypeScript/issues?utf8=%E2%9C%93\&q=milestone%3A%22TypeScript+5.1.3%22+is%3Aclosed+). Downloads are available on: - [NuGet package](https://www.nuget.org/packages/Microsoft.TypeScript.MSBuild) </details> --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), 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](https://github.com/renovatebot/renovate/discussions) if that's undesired. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzNC4xNjAuMCIsInVwZGF0ZWRJblZlciI6IjM0LjE2MC4wIn0=-->
kjuulh changed title from Update dependency @types/node to v18.16.14 to Update dependency @types/node to v18.16.15 2023-05-25 23:07:26 +02:00
kjuulh force-pushed renovate/all from 01fe96ce79 to 376fa0ef20 2023-05-25 23:07:27 +02:00 Compare
kjuulh changed title from Update dependency @types/node to v18.16.15 to Update dependency @types/node to v18.16.16 2023-05-26 22:52:22 +02:00
kjuulh force-pushed renovate/all from 376fa0ef20 to f42eba19d0 2023-05-26 22:52:23 +02:00 Compare
kjuulh changed title from Update dependency @types/node to v18.16.16 to Update all dependencies 2023-05-31 01:45:16 +02:00
kjuulh force-pushed renovate/all from f42eba19d0 to 26daea94c0 2023-05-31 01:45:16 +02:00 Compare
kjuulh force-pushed renovate/all from 26daea94c0 to 4efd4c5a6e 2023-06-08 00:21:16 +02:00 Compare
kjuulh force-pushed renovate/all from 4efd4c5a6e to 2c12f0b28c 2023-06-09 17:08:00 +02:00 Compare
kjuulh force-pushed renovate/all from 2c12f0b28c to 2ba8461417 2023-06-10 04:20:34 +02:00 Compare
kjuulh force-pushed renovate/all from 2ba8461417 to 35931a4e6b 2023-06-13 04:45:17 +02:00 Compare
kjuulh force-pushed renovate/all from 35931a4e6b to 3067073812 2023-06-13 05:39:33 +02:00 Compare
kjuulh force-pushed renovate/all from 3067073812 to 97a703b0bc 2023-06-14 16:32:44 +02:00 Compare
kjuulh force-pushed renovate/all from 97a703b0bc to 3e8f927af3 2023-06-19 15:24:43 +02:00 Compare
kjuulh merged commit 6274fdce41 into main 2023-06-19 15:48:40 +02:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
kjuulh
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: kjuulh/vidow#119
No description provided.
Delete Branch "renovate/all"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?