redux-devtools
redux-devtools copied to clipboard
reduxjs
chore(deps): update all non-major dependencies
This PR contains the following updates:
Release Notes
changesets/changesets (@changesets/cli)
v2.27.7
Patch Changes
-
#1047
d108fa6Thanks @patzick! - Fixed a crash that could occur when depending on a tagged version of another workspace package. -
#1400
dd6e5bbThanks @Andarist! - Fixed a crash that prevented the CLI from running in a scenario when a workspace depends on the root workspace
v2.27.6
Patch Changes
chromaui/addon-visual-tests (@chromatic-com/storybook)
v1.6.1
🐛 Bug Fix
- Fix closing multiple notifications of the same type #329 (@ghengeveld)
- Add backport releases to changelog #327 (@ghengeveld)
Authors: 1
- Gert Hengeveld (@ghengeveld)
v1.6.0
🚀 Enhancement
- Ignore
storybookBuildDirproperty for VTA builds #324 (@ghengeveld)
🐛 Bug Fix
- Replace API polling with browser-native "online" status check #326 (@ghengeveld)
- Add stories for
SidebarBottom#314 (@ghengeveld) - Use modern Yarn and run on port 6004 #325 (@ghengeveld)
- Upgrade some deprecated uses of
@storybook/components#316 (@ghengeveld) - Disallow stopping build after upload step #317 (@ghengeveld)
- Don't auto-expand build eyebrow when canceling build #315 (@ghengeveld)
- Add stories for
TooltipMenucomponent #313 (@ghengeveld)
Authors: 1
- Gert Hengeveld (@ghengeveld)
v1.5.1
🐛 Bug Fix
- Replace API polling with browser-native "online" status check #326 (@ghengeveld)
storybookjs/storybook (@storybook/addon-essentials)
v8.1.11
- Telemetry: Detect Node version - #28299, thanks @yannbf!
- Test: Upgrade deps of @storybook/test - #27862, thanks @kasperpeulen!
v8.1.10
- Addon-interactions: Fix deprecation warnings - #28250, thanks @shilman!
- Test: Upgrade deps of @storybook/test - #27862, thanks @kasperpeulen!
v8.1.9
- Addon-a11y: Workaround for Vite 5.3.0 compat - #28241, thanks @shilman!
- CLI: Add
--no-devoption toinit- #26918, thanks @fastfrwrd! - CLI: Fix
init --skip-install- #28226, thanks @shilman!
v8.1.8
storybookjs/storybook (@storybook/addon-onboarding)
v8.1.11
8.1.11
- Telemetry: Detect Node version - #28299, thanks @yannbf!
- Test: Upgrade deps of @storybook/test - #27862, thanks @kasperpeulen!
v8.1.10
8.1.10
- Addon-interactions: Fix deprecation warnings - #28250, thanks @shilman!
- Test: Upgrade deps of @storybook/test - #27862, thanks @kasperpeulen!
v8.1.9
8.1.9
- Addon-a11y: Workaround for Vite 5.3.0 compat - #28241, thanks @shilman!
- CLI: Add
--no-devoption toinit- #26918, thanks @fastfrwrd! - CLI: Fix
init --skip-install- #28226, thanks @shilman!
v8.1.8
8.1.8
storybookjs/addon-webpack5-compiler-swc (@storybook/addon-webpack5-compiler-swc)
v1.0.4
🐛 Bug Fix
- Set env.bugfixes by default #6 (@kasperpeulen)
Authors: 1
- Kasper Peulen (@kasperpeulen)
typescript-eslint/typescript-eslint (@typescript-eslint/eslint-plugin)
v7.15.0
🚀 Features
-
eslint-plugin: [array-type] detect
Readonly<string[]>case -
eslint-plugin: back-port new rules around empty object types from v8
🩹 Fixes
-
disable
EXPERIMENTAL_useProjectServiceindisabled-type-checkedshared config -
eslint-plugin: [no-unsafe-return] differentiate a types-error any from a true any
-
eslint-plugin: [no-unsafe-call] differentiate a types-error any from a true any
❤️ Thank You
- auvred
- Kim Sang Du
- rgehbt
- Vinccool96
You can read about our versioning strategy and releases on our website.
v7.14.1
🩹 Fixes
-
eslint-plugin: [prefer-nullish-coalescing] treat enums and literals as their underlying primitive types
-
eslint-plugin: [prefer-nullish-coalescing] ensure ternary fix does not remove parens
❤️ Thank You
- Jake Bailey
You can read about our versioning strategy and releases on our website.
v7.14.0
🚀 Features
- support TypeScript 5.5
🩹 Fixes
-
eslint-plugin: [no-extraneous-class] handle abstract members
-
eslint-plugin: [prefer-nullish-coalescing] handle intersected primitive types
-
eslint-plugin: [no-invalid-this] support AccessorProperty
❤️ Thank You
- Brad Zacher
- cm-ayf
- Jake Bailey
- James Zhan
- Joshua Chen
- yoshi2no
You can read about our versioning strategy and releases on our website.
v7.13.1
🩹 Fixes
-
eslint-plugin: [prefer-readonly] refine report locations
-
eslint-plugin: [return-await] support explicit resource management
-
eslint-plugin: [no-unsafe-member-access] differentiate a types-error any from a true any
❤️ Thank You
- Kirk Waiblinger
- Yukihiro Hasegawa
You can read about our versioning strategy and releases on our website.
typescript-eslint/typescript-eslint (@typescript-eslint/parser)
v7.15.0
This was a version bump only for parser to align it with other projects, there were no code changes.
You can read about our versioning strategy and releases on our website.
v7.14.1
This was a version bump only for parser to align it with other projects, there were no code changes.
You can read about our versioning strategy and releases on our website.
v7.14.0
🚀 Features
- support TypeScript 5.5
❤️ Thank You
- Brad Zacher
- cm-ayf
- Jake Bailey
- James Zhan
- Joshua Chen
- yoshi2no
You can read about our versioning strategy and releases on our website.
v7.13.1
This was a version bump only for parser to align it with other projects, there were no code changes.
You can read about our versioning strategy and releases on our website.
electron/electron (electron)
v31.1.0: electron v31.1.0
Release Notes for v31.1.0
Features
Fixes
- Fixed an issue where MessagePorts could close unexpectedly with non-cloneable objects sent via
postMessage. #42580 (Also in 30, 32) - Fixed an issue where
fetch-dependent interfaces could be missing in Web Workers withnodeIntegrationInWorkerenabled. #42597 (Also in 30, 32)
Other Changes
- Updated Chromium to 126.0.6478.114. #42584
v31.0.2: electron v31.0.2
Release Notes for v31.0.2
Fixes
- Fixed an issue where
navigator.usb.getDevices()could crash in some circumstances. #42462 (Also in 29, 30)
Other Changes
- Fixed crash in gpu process when software compositing is enabled on linux with x11 platform. #42570 (Also in 29, 30, 32)
- Updated Chromium to 126.0.6478.61. #42503
v31.0.1: electron v31.0.1
Release Notes for v31.0.1
Fixes
evanw/esbuild (esbuild)
v0.23.0
This release deliberately contains backwards-incompatible changes. To avoid automatically picking up releases like this, you should either be pinning the exact version of esbuild in your package.json file (recommended) or be using a version range syntax that only accepts patch upgrades such as ^0.22.0 or ~0.22.0. See npm's documentation about semver for more information.
-
Revert the recent change to avoid bundling dependencies for node (#3819)
This release reverts the recent change in version 0.22.0 that made
--packages=externalthe default behavior with--platform=node. The default is now back to--packages=bundle.I've just been made aware that Amazon doesn't pin their dependencies in their "AWS CDK" product, which means that whenever esbuild publishes a new release, many people (potentially everyone?) using their SDK around the world instantly starts using it without Amazon checking that it works first. This change in version 0.22.0 happened to break their SDK. I'm amazed that things haven't broken before this point. This revert attempts to avoid these problems for Amazon's customers. Hopefully Amazon will pin their dependencies in the future.
In addition, this is probably a sign that esbuild is used widely enough that it now needs to switch to a more complicated release model. I may have esbuild use a beta channel model for further development.
-
Fix preserving collapsed JSX whitespace (#3818)
When transformed, certain whitespace inside JSX elements is ignored completely if it collapses to an empty string. However, the whitespace should only be ignored if the JSX is being transformed, not if it's being preserved. This release fixes a bug where esbuild was previously incorrectly ignoring collapsed whitespace with
--jsx=preserve. Here is an example:// Original code <Foo> <Bar /> </Foo> // Old output (with --jsx=preserve) <Foo><Bar /></Foo>; // New output (with --jsx=preserve) <Foo> <Bar /> </Foo>;
v0.22.0
This release deliberately contains backwards-incompatible changes. To avoid automatically picking up releases like this, you should either be pinning the exact version of esbuild in your package.json file (recommended) or be using a version range syntax that only accepts patch upgrades such as ^0.21.0 or ~0.21.0. See npm's documentation about semver for more information.
-
Omit packages from bundles by default when targeting node (#1874, #2830, #2846, #2915, #3145, #3294, #3323, #3582, #3809, #3815)
This breaking change is an experiment. People are commonly confused when using esbuild to bundle code for node (i.e. for
--platform=node) because some packages may not be intended for bundlers, and may use node-specific features that don't work with a bundler. Even though esbuild's "getting started" instructions say to use--packages=externalto work around this problem, many people don't read the documentation and don't do this, and are then confused when it doesn't work. So arguably this is a bad default behavior for esbuild to have if people keep tripping over this.With this release, esbuild will now omit packages from the bundle by default when the platform is
node(i.e. the previous behavior of--packages=externalis now the default in this case). Note that your dependencies must now be present on the file system when your bundle is run. If you don't want this behavior, you can do--packages=bundleto allow packages to be included in the bundle (i.e. the previous default behavior). Note that--packages=bundledoesn't mean all packages are bundled, just that packages are allowed to be bundled. You can still exclude individual packages from the bundle using--external:even when--packages=bundleis present.The
--packages=setting considers all import paths that "look like" package imports in the original source code to be package imports. Specifically import paths that don't start with a path segment of/or.or..are considered to be package imports. The only two exceptions to this rule are subpath imports (which start with a#character) and TypeScript path remappings viapathsand/orbaseUrlintsconfig.json(which are applied first). -
Drop support for older platforms (#3802)
This release drops support for the following operating systems:
- Windows 7
- Windows 8
- Windows Server 2008
- Windows Server 2012
This is because the Go programming language dropped support for these operating system versions in Go 1.21, and this release updates esbuild from Go 1.20 to Go 1.22.
Note that this only affects the binary esbuild executables that are published to the
esbuildnpm package. It's still possible to compile esbuild's source code for these older operating systems. If you need to, you can compile esbuild for yourself using an older version of the Go compiler (before Go version 1.21). That might look something like this:git clone https://github.com/evanw/esbuild.git cd esbuild go build ./cmd/esbuild ./esbuild.exe --versionIn addition, this release increases the minimum required node version for esbuild's JavaScript API from node 12 to node 18. Node 18 is the oldest version of node that is still being supported (see node's release schedule for more information). This increase is because of an incompatibility between the JavaScript that the Go compiler generates for the
esbuild-wasmpackage and versions of node before node 17.4 (specifically thecrypto.getRandomValuesfunction). -
Update
await usingbehavior to match TypeScriptTypeScript 5.5 subtly changes the way
await usingbehaves. This release updates esbuild to match these changes in TypeScript. You can read more about these changes in microsoft/TypeScript#58624. -
Allow
es2024as a target environmentThe ECMAScript 2024 specification was just approved, so it has been added to esbuild as a possible compilation target. You can read more about the features that it adds here: https://2ality.com/2024/06/ecmascript-2024.html. The only addition that's relevant for esbuild is the regular expression
/vflag. With--target=es2024, regular expressions that use the/vflag will now be passed through untransformed instead of being transformed into a call tonew RegExp. -
Publish binaries for OpenBSD on 64-bit ARM (#3665, #3674)
With this release, you should now be able to install the
esbuildnpm package in OpenBSD on 64-bit ARM, such as on an Apple device with an M1 chip.This was contributed by @ikmckenz.
-
Publish binaries for WASI (WebAssembly System Interface) preview 1 (#3300, #3779)
The upcoming WASI (WebAssembly System Interface) standard is going to be a way to run WebAssembly outside of a JavaScript host environment. In this scenario you only need a
.wasmfile without any supporting JavaScript code. Instead of JavaScript providing the APIs for the host environment, the WASI standard specifies a "system interface" that WebAssembly code can access directly (e.g. for file system access).Development versions of the WASI specification are being released using preview numbers. The people behind WASI are currently working on preview 2 but the Go compiler has released support for preview 1, which from what I understand is now considered an unsupported legacy release. However, some people have requested that esbuild publish binary executables that support WASI preview 1 so they can experiment with them.
This release publishes esbuild
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 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 Mend Renovate. View repository job log here.
![renovate[bot] avatar](https://avatars.githubusercontent.com/in/2740?v=4 "Published by a pub.dev verified publisher"){kind=small}