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.

Sign up for GitHub

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

Jump to bottom

fix(deps): update all non-major dependencies #209

Merged
merged 1 commit into from
Jul 21, 2024
Merged

fix(deps): update all non-major dependencies #209

merged 1 commit into from
Jul 21, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented May 27, 2024 •
edited
Loading

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@emotion/react (source) ^11.11.4 -> ^11.13.0 age adoption passing confidence
@emotion/styled (source) ^11.11.5 -> ^11.13.0 age adoption passing confidence
@generouted/react-router ^1.19.4 -> ^1.19.6 age adoption passing confidence
@playwright/test (source) ^1.44.0 -> ^1.45.2 age adoption passing confidence
@swc/core (source) ^1.5.7 -> ^1.7.0 age adoption passing confidence
@swc/plugin-emotion ^3.0.4 -> ^3.0.10 age adoption passing confidence
@swc/plugin-styled-components ^2.0.6 -> ^2.0.10 age adoption passing confidence
@types/node (source) 20.11.5 -> 20.14.11 age adoption passing confidence
@types/react (source) ^18.3.2 -> ^18.3.3 age adoption passing confidence
esbuild ^0.21.3 -> ^0.23.0 age adoption passing confidence
react-router-dom (source) ^6.23.1 -> ^6.25.1 age adoption passing confidence
styled-components (source) ^6.1.11 -> ^6.1.12 age adoption passing confidence
typescript (source) ^5.4.5 -> ^5.5.3 age adoption passing confidence
vite (source) ^5.2.11 -> ^5.3.4 age adoption passing confidence

Release Notes

emotion-js/emotion (@​emotion/react)

v11.13.0

Compare Source

v11.12.0

Compare Source

oedotme/generouted (@​generouted/react-router)

v1.19.6

Compare Source

Commits

Changelog: oedotme/generouted@v1.19.5...v1.19.6

v1.19.5

Compare Source

Commits

Changelog: oedotme/generouted@v1.19.4...v1.19.5

microsoft/playwright (@​playwright/test)

v1.45.2

Compare Source

v1.45.1

Compare Source

v1.45.0

Compare Source

v1.44.1

Compare Source

Highlights

https://github.com/microsoft/playwright/issues/30779 - [REGRESSION]: When using video: 'on' with VSCode extension the browser got closed
https://github.com/microsoft/playwright/issues/30755 - [REGRESSION]: Electron launch with spaces inside executablePath didn't workhttps://github.com/microsoft/playwright/issues/307700 - [REGRESSION]: Mask elements outside of viewport when creating fullscreen screenshots didn't worhttps://github.com/microsoft/playwright/issues/3085858 - [REGRESSION]: ipv6 got shown instead of localhost in show-trace/show-report

Browser Versions

  • Chromium 125.0.6422.14
  • Mozilla Firefox 125.0.1
  • WebKit 17.4

This version was also tested against the following stable channels:

  • Google Chrome 124
  • Microsoft Edge 124
swc-project/swc (@​swc/core)

v1.7.0

Compare Source

Bug Fixes
Documentation

  • (allocator) Mention oxc_allocator (be99ce0)

  • (contributing) Fix deno installation url (#​9249) (ff5bbda)

  • (es/minifier) Add contributing section (e22f3ba)

Features
Miscellaneous Tasks
Performance
Refactor
Testing
Pers

v1.6.13

Compare Source

Bug Fixes
Features
Testing

v1.6.12

Compare Source

Bug Fixes
Features
Performance
Refactor

v1.6.7

Compare Source

Bug Fixes
Documentation
  • Use @swc/counter for 3rd-party download count (026ff7e)
Features
Performance
Refactor
  • (es/typescript) Extract type annotation proposal out (#​9127) (dfee5f8)
Testing
Build

v1.6.6

Compare Source

Bug Fixes
Performance

v1.6.5

Compare Source

v1.6.4

Compare Source

Features
Miscellaneous Tasks
Performance
Refactor

v1.6.3

Compare Source

Bug Fixes
Performance
Refactor

v1.6.1

Compare Source

Bug Fixes
Performance

v1.6.0

Compare Source

Features
Performance
Refactor
Testing

v1.5.29

Compare Source

Bug Fixes
Performance

v1.5.28

Compare Source

Bug Fixes

v1.5.27

Compare Source

v1.5.25

Compare Source

Bug Fixes
Features
Performance

v1.5.24

Compare Source

v1.5.23

Compare Source

Bug Fixes

v1.5.22

Compare Source

v1.5.20

Compare Source

v1.5.19

Compare Source

v1.5.11

Compare Source

evanw/esbuild (esbuild)

v0.23.0

Compare Source

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=external the 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

Compare Source

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=external to 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=external is 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=bundle to allow packages to be included in the bundle (i.e. the previous default behavior). Note that --packages=bundle doesn'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=bundle is 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 via paths and/or baseUrl in tsconfig.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 esbuild npm 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 --version

    In 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-wasm package and versions of node before node 17.4 (specifically the crypto.getRandomValues function).

  • Update await using behavior to match TypeScript

    TypeScript 5.5 subtly changes the way await using behaves. This release updates esbuild to match these changes in TypeScript. You can read more about these changes in microsoft/TypeScript#58624.

  • Allow es2024 as a target environment

    The 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 /v flag. With --target=es2024, regular expressions that use the /v flag will now be passed through untransformed instead of being transformed into a call to new RegExp.

  • Publish binaries for OpenBSD on 64-bit ARM (#​3665, #​3674)

    With this release, you should now be able to install the esbuild npm 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 .wasm file 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 precompiled for WASI preview 1 to the @esbuild/wasi-preview1 package on npm (specifically the file @esbuild/wasi-preview1/esbuild.wasm). This binary executable has not been tested and won't be officially supported, as it's for an old preview release of a specification that has since moved in another direction. If it works for you, great! If not, then you'll likely have to wait for the ecosys

Configuration

📅 Schedule: Branch creation - "before 4am on Monday" (UTC), 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 renovate bot added the dependencies Pull requests that update a dependency file label May 27, 2024
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 9 times, most recently from 60db0a5 to 80a4c73 Compare June 4, 2024 01:03
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 7 times, most recently from 66780fd to b66719c Compare June 11, 2024 09:14
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 10 times, most recently from a68969b to c9398d8 Compare June 19, 2024 18:02
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 3 times, most recently from 8fcab6c to cef490f Compare June 22, 2024 07:54
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 7 times, most recently from 4e2a48a to d9d8332 Compare July 1, 2024 07:00
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 10 times, most recently from cabb6a3 to 291b0fb Compare July 7, 2024 05:00
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 291b0fb to e0a9b10 Compare July 8, 2024 19:33
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 8 times, most recently from 9b1ba60 to 9f82c04 Compare July 20, 2024 08:18
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 9f82c04 to 8d647f3 Compare July 21, 2024 16:20
@ArnaudBarre ArnaudBarre merged commit 3029ffb into main Jul 21, 2024
1 check passed
@ArnaudBarre ArnaudBarre deleted the renovate/all-minor-patch branch July 21, 2024 16:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@ArnaudBarre