mend-for-github-com[bot]
commented
1 year ago ⚠ 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: yarn.lock
No /opt/buildpack/tools/yarn-slim/1.22.19/bin/yarn defined - aborting
This PR contains the following updates:
3.6.0->3.7.0By merging this PR, the issue #23 will be automatically resolved and closed:
Release Notes
reduxjs/redux (redux)
### [`v3.7.0`](https://togithub.com/reduxjs/redux/releases/tag/v3.7.0) [Compare Source](https://togithub.com/reduxjs/redux/compare/v3.6.0...v3.7.0) ##### Another long break! Oh, hey! I didn't see you sitting there. You look bored. How about a Redux release to spice things up? Not a huge set of changes to report here. The biggest change, and the reason for the minor bump, is the UMD build is now done via [Rollup](https://rollupjs.org/). One big advantage is more readable code in the bundle. Rollup does "scope hoisting", which is a fancy term for putting every module at the top level of the file. Other than a surrounding [IIFE](https://en.wikipedia.org/wiki/Immediately-invoked_function_expression), all of the code in Redux all lives together. You can compare the two here: [Rollup UMD build](https://unpkg.com/redux@3.7.0/dist/redux.js)\ vs\ [Webpack UMD build](https://unpkg.com/redux@3.6.0/dist/redux.js) There is also a cost savings of 30,811 vs 26,880 bytes, and 6,999 vs 5,995 bytes minified. Redux is already a small library, and this helps shave some extra bytes for our UMD users. One thing to note is that Webpack has introduced it's own scope hoisting feature in 3.0 beta. So, this isn't intended as an indictment of Webpack. You should continue to use it in your own apps. The adage of "Webpack is for apps, Rollup is for libraries" definitely holds true. It still has a superior developer experience with hot module reloading and webpack-dev-server. But use whatever makes sense for your project, not just whatever we use. 😄 We're also looking at applying this to the NPM bundle. The main motivation is again more readable code in your bundles. Instead of [transpilation oddities from Babel](https://unpkg.com/redux@3.6.0/lib/index.js), you will end up with [a single clean file](https://gist.githubusercontent.com/TrySound/987213f06dd9b29ca2cecbdea55d8047/raw/89f48440cb847fba62afb6074d876f419c68102e/redux.js), which should be easier to read through and debug. It's currently scheduled for the big, mythical 4.0 release and you can follow along in [#2358](https://togithub.com/reduxjs/redux/issues/2358) ##### [Changes](https://togithub.com/reactjs/redux/compare/v3.6.0...v3.7.0) - Build UMD with rollup ([#2283](https://togithub.com/reduxjs/redux/issues/2283) by [@TrySound](https://togithub.com/TrySound)) - Warn when bindActionCreators encounters non-function property ([#2279](https://togithub.com/reduxjs/redux/issues/2279) by [@artgillespie](https://togithub.com/artgillespie)) - Update variables to ES6 ([#2169](https://togithub.com/reduxjs/redux/issues/2169) by [@dfrownfelter](https://togithub.com/dfrownfelter)) - Remove filtering inside compose ([#2167](https://togithub.com/reduxjs/redux/issues/2167) by [@istarkov](https://togithub.com/istarkov)) - Simplify compose ([#2147](https://togithub.com/reduxjs/redux/issues/2147) by [@JoeCortopassi](https://togithub.com/JoeCortopassi))