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

chore(deps): update all non-major dependencies #5957

Merged
merged 2 commits into from
Jul 1, 2024
Merged

chore(deps): update all non-major dependencies #5957

merged 2 commits into from
Jul 1, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jun 24, 2024 •
edited
Loading

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@antfu/eslint-config ^2.21.1 -> ^2.21.2 age adoption passing confidence
@iconify-json/carbon ^1.1.35 -> ^1.1.36 age adoption passing confidence
@playwright/test (source) ^1.44.1 -> ^1.45.0 age adoption passing confidence
@shikijs/vitepress-twoslash (source) ^1.7.0 -> ^1.10.0 age adoption passing confidence
@testing-library/dom ^10.1.0 -> ^10.2.0 age adoption passing confidence
@types/d3-force (source) ^3.0.9 -> ^3.0.10 age adoption passing confidence
@types/micromatch (source) ^4.0.7 -> ^4.0.9 age adoption passing confidence
@types/node (source) ^20.14.2 -> ^20.14.9 age adoption passing confidence
d3-graph-controller (source) ^3.0.9 -> ^3.0.10 age adoption passing confidence
esbuild ^0.21.5 -> ^0.22.0 age adoption passing confidence
eslint (source) ^9.5.0 -> ^9.6.0 age adoption passing confidence
happy-dom ^14.12.0 -> ^14.12.3 age adoption passing confidence
istanbul-lib-source-maps (source) ^5.0.4 -> ^5.0.5 age adoption passing confidence
playwright (source) ^1.44.1 -> ^1.45.0 age adoption passing confidence
playwright-core (source) ^1.44.1 -> ^1.45.0 age adoption passing confidence
rollup-plugin-license ^3.4.0 -> ^3.5.1 age adoption passing confidence
tsx (source) ^4.15.6 -> ^4.16.0 age adoption passing confidence
typescript (source) ^5.4.5 -> ^5.5.2 age adoption passing confidence
unplugin-vue-components ^0.27.0 -> ^0.27.2 age adoption passing confidence
vite-plugin-pages ^0.32.2 -> ^0.32.3 age adoption passing confidence
vue (source) ^3.4.29 -> ^3.4.31 age adoption passing confidence
vue-router ^4.3.3 -> ^4.4.0 age adoption passing confidence
webdriverio (source) ^8.38.2 -> ^8.39.0 age adoption passing confidence
zx ^8.1.2 -> ^8.1.3 age adoption passing confidence

Release Notes

antfu/eslint-config (@​antfu/eslint-config)

v2.21.2

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub
microsoft/playwright (@​playwright/test)

v1.45.0

Compare Source

shikijs/shiki (@​shikijs/vitepress-twoslash)

v1.10.0

Compare Source

   🚀 Features
   🐞 Bug Fixes
  • Expose createCssVariablesTheme in shiki/core to avoid side-effects  -  by @​antfu (abe63)
    View changes on GitHub

v1.9.1

Compare Source

   🚀 Features
    View changes on GitHub

v1.9.0

Compare Source

   🚨 Breaking Changes
    View changes on GitHub

v1.8.0

Compare Source

   🚀 Features
    View changes on GitHub
testing-library/dom-testing-library (@​testing-library/dom)

v10.2.0

Compare Source

Features
  • Support anonymous custom elements when pretty printing DOM (#​1319) (0a8ad65)
DerYeger/yeger (d3-graph-controller)

v3.0.10

Compare Source

Patch Changes
evanw/esbuild (esbuild)

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 ecosystem to evolve before using esbuild with WASI. For example, it sounds like perhaps WASI preview 1 doesn't include support for opening network sockets so esbuild's local development server is unlikely to work with WASI preview 1.

  • Warn about onResolve plugins not setting a path (#​3790)

    Plugins that return values from onResolve without resolving the path (i.e. without setting either path or external: true) will now cause a warning. This is because esbuild only uses return values from onResolve if it successfully resolves the path, and it's not good for invalid input to be silently ignored.

  • Add a new Go API for running the CLI with plugins (#​3539)

    With esbuild's Go API, you can now call cli.RunWithPlugins(args, plugins) to pass an array of esbuild plugins to be used during the build process. This allows you to create a CLI that behaves similarly to esbuild's CLI but with additional Go plugins enabled.

    This was contributed by @​edewit.

eslint/eslint (eslint)

v9.6.0

Compare Source

capricorn86/happy-dom (happy-dom)

v14.12.3

Compare Source

👷‍♂️ Patch fixes
  • Element.insertBefore works when the node is already inserted - In task #​1429

v14.12.2

Compare Source

👷‍♂️ Patch fixes
  • Fixes problem related to the cookie container using the wrong path when caching cookies - By @​matcic in task #​1455

v14.12.1

Compare Source

👷‍♂️ Patch fixes
  • Fixes problem related to React click handler with preventDefault not preventing navigation - By @​amitdahan in task #​1464
istanbuljs/istanbuljs (istanbul-lib-source-maps)

v5.0.5

Compare Source

Bug Fixes
  • istanbul-lib-source-maps to preserve implicit else when sourcemaps are used (#​706) (d16a155)
mjeanroy/rollup-plugin-license (rollup-plugin-license)

v3.5.1

Compare Source

v3.5.0

Compare Source

v3.4.1

Compare Source

privatenumber/tsx (tsx)

v4.16.0

Compare Source

v4.15.9

Compare Source

v4.15.8

Compare Source

v4.15.7

Compare Source

Bug Fixes

This release is also available on:

Microsoft/TypeScript (typescript)

v5.5.2

Compare Source

unplugin/unplugin-vue-components (unplugin-vue-components)

v0.27.2

Compare Source

No significant changes

    View changes on GitHub

v0.27.1

Compare Source

   🚀 Features
    View changes on GitHub
hannoeru/vite-plugin-pages (vite-plugin-pages)

v0.32.3

Compare Source

   🚀 Features
    View changes on GitHub
vuejs/core (vue)

v3.4.31

Compare Source

Bug Fixes
Reverts
  • Revert "fix(reactivity): avoid infinite loop when render access a side effect computed (#​11135)" (e0df985)
  • Revert "fix(reactivity): fix side effect computed dirty level (#​11183)" (6c303ea), closes #​11183

v3.4.30

Compare Source

Bug Fixes
Performance Improvements
vuejs/router (vue-router)

v4.4.0

Compare Source

Please refer to CHANGELOG.md for details.

webdriverio/webdriverio (webdriverio)

v8.39.0

Compare Source

v8.39.0 (2024-06-18)

💅 Polish
📝 Documentation
Committers: 5
google/zx (zx)

v8.1.3

Compare Source

Nothing special today. We just keep improving the implementation.

Features

import {$} from 'zx'
  • zx/cli exports its inners to allow more advanced usage.
    Imagine, your own CLI tool that uses zx as a base:
    #​828
#!/usr/bin/env node

import './index.mjs'
import {main} from 'zx/cli'

main()
  • Provide intermediate store configuration for fine-grained control of memory usage.
    #​650, #​849
const getFixedSizeArray = (size) => {
  const arr = []
  return new Proxy(arr, {
    get: (target, prop) =>
      prop === 'push' && arr.length >= size
        ? () => {}
        : target[prop],
  })
}
const store = {
  stdout: getFixedSizeArray(1),
  stderr: getFixedSizeArray(1),
  stdall: getFixedSizeArray(0),
}

const p = await $({ store })`echo foo`

p.stdout.trim() //  'foo'
p.toString()    // ''
  • Introduced sync methods for ps:
    #​840
import { ps } from 'zx'

const list1 = await ps()
const list2 = await tree()

// new methods
const list3 = ps.sync()
const list4 = tree.sync()

Chore

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.

@AriPerkkio AriPerkkio mentioned this pull request Jun 24, 2024
Merged
6 tasks
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 17 times, most recently from bd0353a to 0cad7a0 Compare July 1, 2024 06:09
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 0cad7a0 to 702588a Compare July 1, 2024 09:04
@renovate Renovate
Copy link
Contributor Author

renovate bot commented Jul 1, 2024

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

@sheremet-va sheremet-va merged commit 05d5f38 into main Jul 1, 2024
16 checks passed
@sheremet-va sheremet-va deleted the renovate/all-minor-patch branch July 1, 2024 16:10
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
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
1 participant
@sheremet-va