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 #7363

Merged
merged 6 commits into from
Feb 11, 2025
Merged

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

merged 6 commits into from
Feb 11, 2025
+780 −471

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jan 27, 2025 •
edited
Loading

This PR contains the following updates:

Package Change Age Adoption Passing Confidence Type Update
@antfu/ni ^23.2.0 -> ^23.3.1 age adoption passing confidence devDependencies minor
@iconify-json/carbon ^1.2.5 -> ^1.2.6 age adoption passing confidence devDependencies patch
@playwright/test (source) ^1.49.1 -> ^1.50.1 age adoption passing confidence devDependencies minor
@shikijs/transformers (source) ^1.29.1 -> ^1.29.2 age adoption passing confidence devDependencies patch
@shikijs/vitepress-twoslash (source) ^1.29.1 -> ^1.29.2 age adoption passing confidence devDependencies patch
@types/node (source) ^22.10.9 -> ^22.13.1 age adoption passing confidence devDependencies minor
@types/ws (source) ^8.5.13 -> ^8.5.14 age adoption passing confidence devDependencies patch
@ungap/structured-clone ^1.2.1 -> ^1.3.0 age adoption passing confidence devDependencies minor
d3-graph-controller (source) ^3.0.12 -> ^3.0.13 age adoption passing confidence devDependencies patch
esbuild ^0.24.2 -> ^0.25.0 age adoption passing confidence devDependencies minor
happy-dom ^16.7.2 -> ^16.8.1 age adoption passing confidence devDependencies minor
loupe ^3.1.2 -> ^3.1.3 age adoption passing confidence dependencies patch
playwright (source) ^1.49.1 -> ^1.50.1 age adoption passing confidence devDependencies minor
playwright-core (source) ^1.49.1 -> ^1.50.1 age adoption passing confidence devDependencies minor
pnpm (source) 9.15.4 -> 9.15.5 age adoption passing confidence packageManager patch
rollup (source) ^4.31.0 -> ^4.34.6 age adoption passing confidence devDependencies minor
rollup-plugin-esbuild ^6.1.1 -> ^6.2.0 age adoption passing confidence devDependencies minor
tj-actions/changed-files v45.0.6 -> v45.0.7 age adoption passing confidence action patch
vitepress-plugin-tabs (source) ^0.5.0 -> ^0.6.0 age adoption passing confidence devDependencies minor
zx (source) ^8.3.0 -> ^8.3.2 age adoption passing confidence devDependencies patch

Release Notes

antfu-collective/ni (@​antfu/ni)

v23.3.1

Compare Source

   🚀 Features
    View changes on GitHub

v23.3.0

Compare Source

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

v1.50.1

Compare Source

v1.50.0

Compare Source

Test runner

  • New option timeout allows specifying a maximum run time for an individual test step. A timed-out step will fail the execution of the test.

    test('some test', async ({ page }) => {
  await test.step('a step', async () => {
    // This step can time out separately from the test
  }, { timeout: 1000 });
});

  • New method test.step.skip() to disable execution of a test step.

    test('some test', async ({ page }) => {
  await test.step('before running step', async () => {
    // Normal step
  });

  await test.step.skip('not yet ready', async () => {
    // This step is skipped
  });

  await test.step('after running step', async () => {
    // This step still runs even though the previous one was skipped
  });
});

  • Expanded expect(locator).toMatchAriaSnapshot() to allow storing of aria snapshots in separate YAML files.

  • Added method expect(locator).toHaveAccessibleErrorMessage() to assert the Locator points to an element with a given aria errormessage.

  • Option testConfig.updateSnapshots added the configuration enum changed. changed updates only the snapshots that have changed, whereas all now updates all snapshots, regardless of whether there are any differences.

  • New option testConfig.updateSourceMethod defines the way source code is updated when testConfig.updateSnapshots is configured. Added overwrite and 3-way modes that write the changes into source code, on top of existing patch mode that creates a patch file.

    npx playwright test --update-snapshots=changed --update-source-method=3way

  • Option testConfig.webServer added a gracefulShutdown field for specifying a process kill signal other than the default SIGKILL.

  • Exposed testStep.attachments from the reporter API to allow retrieval of all attachments created by that step.

UI updates

  • Updated default HTML reporter to improve display of attachments.
  • New button for picking elements to produce aria snapshots.
  • Additional details (such as keys pressed) are now displayed alongside action API calls in traces.
  • Display of canvas content in traces is error-prone. Display is now disabled by default, and can be enabled via the Display canvas content UI setting.
  • Call and Network panels now display additional time information.

Breaking

Browser Versions

  • Chromium 133.0.6943.16
  • Mozilla Firefox 134.0
  • WebKit 18.2

This version was also tested against the following stable channels:

  • Google Chrome 132
  • Microsoft Edge 132
shikijs/shiki (@​shikijs/transformers)

v1.29.2

Compare Source

   🚨 Breaking Changes
   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub
ungap/structured-clone (@​ungap/structured-clone)

v1.3.0

Compare Source

DerYeger/yeger (d3-graph-controller)

v3.0.13

Compare Source

Patch Changes
evanw/esbuild (esbuild)

v0.25.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.24.0 or ~0.24.0. See npm's documentation about semver for more information.

  • Restrict access to esbuild's development server (GHSA-67mh-4wv8-2f99)

    This change addresses esbuild's first security vulnerability report. Previously esbuild set the Access-Control-Allow-Origin header to * to allow esbuild's development server to be flexible in how it's used for development. However, this allows the websites you visit to make HTTP requests to esbuild's local development server, which gives read-only access to your source code if the website were to fetch your source code's specific URL. You can read more information in the report.

    Starting with this release, CORS will now be disabled, and requests will now be denied if the host does not match the one provided to --serve=. The default host is 0.0.0.0, which refers to all of the IP addresses that represent the local machine (e.g. both 127.0.0.1 and 192.168.0.1). If you want to customize anything about esbuild's development server, you can put a proxy in front of esbuild and modify the incoming and/or outgoing requests.

    In addition, the serve() API call has been changed to return an array of hosts instead of a single host string. This makes it possible to determine all of the hosts that esbuild's development server will accept.

    Thanks to @​sapphi-red for reporting this issue.

  • Delete output files when a build fails in watch mode (#​3643)

    It has been requested for esbuild to delete files when a build fails in watch mode. Previously esbuild left the old files in place, which could cause people to not immediately realize that the most recent build failed. With this release, esbuild will now delete all output files if a rebuild fails. Fixing the build error and triggering another rebuild will restore all output files again.

  • Fix correctness issues with the CSS nesting transform (#​3620, #​3877, #​3933, #​3997, #​4005, #​4037, #​4038)

    This release fixes the following problems:

    • Naive expansion of CSS nesting can result in an exponential blow-up of generated CSS if each nesting level has multiple selectors. Previously esbuild sometimes collapsed individual nesting levels using :is() to limit expansion. However, this collapsing wasn't correct in some cases, so it has been removed to fix correctness issues.

      /* Original code */
.parent {
  > .a,
  > .b1 > .b2 {
    color: red;
  }
}

/* Old output (with --supported:nesting=false) */
.parent > :is(.a, .b1 > .b2) {
  color: red;
}

/* New output (with --supported:nesting=false) */
.parent > .a,
.parent > .b1 > .b2 {
  color: red;
}

      Thanks to @​tim-we for working on a fix.

    • The & CSS nesting selector can be repeated multiple times to increase CSS specificity. Previously esbuild ignored this possibility and incorrectly considered && to have the same specificity as &. With this release, this should now work correctly:

      /* Original code (color should be red) */
div {
  && { color: red }
  & { color: blue }
}

/* Old output (with --supported:nesting=false) */
div {
  color: red;
}
div {
  color: blue;
}

/* New output (with --supported:nesting=false) */
div:is(div) {
  color: red;
}
div {
  color: blue;
}

      Thanks to @​CPunisher for working on a fix.

    • Previously transforming nested CSS incorrectly removed leading combinators from within pseudoclass selectors such as :where(). This edge case has been fixed and how has test coverage.

      /* Original code */
a b:has(> span) {
  a & {
    color: green;
  }
}

/* Old output (with --supported:nesting=false) */
a :is(a b:has(span)) {
  color: green;
}

/* New output (with --supported:nesting=false) */
a :is(a b:has(> span)) {
  color: green;
}

      This fix was contributed by @​NoremacNergfol.

    • The CSS minifier contains logic to remove the & selector when it can be implied, which happens when there is only one and it's the leading token. However, this logic was incorrectly also applied to selector lists inside of pseudo-class selectors such as :where(). With this release, the minifier will now avoid applying this logic in this edge case:

      /* Original code */
.a {
  & .b { color: red }
  :where(& .b) { color: blue }
}

/* Old output (with --minify) */
.a{.b{color:red}:where(.b){color:#​00f}}

/* New output (with --minify) */
.a{.b{color:red}:where(& .b){color:#​00f}}

  • Fix some correctness issues with source maps (#​1745, #​3183, #​3613, #​3982)

    Previously esbuild incorrectly treated source map path references as file paths instead of as URLs. With this release, esbuild will now treat source map path references as URLs. This fixes the following problems with source maps:

    • File names in sourceMappingURL that contained a space previously did not encode the space as %20, which resulted in JavaScript tools (including esbuild) failing to read that path back in when consuming the generated output file. This should now be fixed.

    • Absolute URLs in sourceMappingURL that use the file:// scheme previously attempted to read from a folder called file:. These URLs should now be recognized and parsed correctly.

    • Entries in the sources array in the source map are now treated as URLs instead of file paths. The correct behavior for this is much more clear now that source maps has a formal specification. Many thanks to those who worked on the specification.

  • Fix incorrect package for @esbuild/netbsd-arm64 (#​4018)

    Due to a copy+paste typo, the binary published to @esbuild/netbsd-arm64 was not actually for arm64, and didn't run in that environment. This release should fix running esbuild in that environment (NetBSD on 64-bit ARM). Sorry about the mistake.

  • Fix a minification bug with bitwise operators and bigints (#​4065)

    This change removes an incorrect assumption in esbuild that all bitwise operators result in a numeric integer. That assumption was correct up until the introduction of bigints in ES2020, but is no longer correct because almost all bitwise operators now operate on both numbers and bigints. Here's an example of the incorrect minification:

    // Original code
if ((a & b) !== 0) found = true

// Old output (with --minify)
a&b&&(found=!0);

// New output (with --minify)
(a&b)!==0&&(found=!0);

  • Fix esbuild incorrectly rejecting valid TypeScript edge case (#​4027)

    The following TypeScript code is valid:

    export function open(async?: boolean): void {
  console.log(async as boolean)
}

    Before this version, esbuild would fail to parse this with a syntax error as it expected the token sequence async as ... to be the start of an async arrow function expression async as => .... This edge case should be parsed correctly by esbuild starting with this release.

  • Transform BigInt values into constructor calls when unsupported (#​4049)

    Previously esbuild would refuse to compile the BigInt literals (such as 123n) if they are unsupported in the configured target environment (such as with --target=es6). The rationale was that they cannot be polyfilled effectively because they change the behavior of JavaScript's arithmetic operators and JavaScript doesn't have operator overloading.

    However, this prevents using esbuild with certain libraries that would otherwise work if BigInt literals were ignored, such as with old versions of the buffer library before the library fixed support for running in environments without BigInt support. So with this release, esbuild will now turn BigInt literals into BigInt constructor calls (so 123n becomes BigInt(123)) and generate a warning in this case. You can turn off the warning with --log-override:bigint=silent or restore the warning to an error with --log-override:bigint=error if needed.

  • Change how console API dropping works (#​4020)

    Previously the --drop:console feature replaced all method calls off of the console global with undefined regardless of how long the property access chain was (so it applied to console.log() and console.log.call(console) and console.log.not.a.method()). However, it was pointed out that this breaks uses of console.log.bind(console). That's also incompatible with Terser's implementation of the feature, which is where this feature originally came from (it does support bind). So with this release, using this feature with esbuild will now only replace one level of method call (unless extended by call or apply) and will replace the method being called with an empty function in complex cases:

    // Original code
const x = console.log('x')
const y = console.log.call(console, 'y')
const z = console.log.bind(console)('z')

// Old output (with --drop-console)
const x = void 0;
const y = void 0;
const z = (void 0)("z");

// New output (with --drop-console)
const x = void 0;
const y = void 0;
const z = (() => {
}).bind(console)("z");

    This should more closely match Terser's existing behavior.

  • Allow BigInt literals as define values

    With this release, you can now use BigInt literals as define values, such as with --define:FOO=123n. Previously trying to do this resulted in a syntax error.

  • Fix a bug with resolve extensions in node_modules (#​4053)

    The --resolve-extensions= option lets you specify the order in which to try resolving implicit file extensions. For complicated reasons, esbuild reorders TypeScript file extensions after JavaScript ones inside of node_modules so that JavaScript source code is always preferred to TypeScript source code inside of dependencies. However, this reordering had a bug that could accidentally change the relative order of TypeScript file extensions if one of them was a prefix of the other. That bug has been fixed in this release. You can see the issue for details.

  • Better minification of statically-determined switch cases (#​4028)

    With this release, esbuild will now try to trim unused code within switch statements when the test expression and case expressions are primitive literals. This can arise when the test expression is an identifier that is substituted for a primitive literal at compile time. For example:

    // Original code
switch (MODE) {
  case 'dev':
    installDevToolsConsole()
    break
  case 'prod':
    return
  default:
    throw new Error
}

// Old output (with --minify '--define:MODE="prod"')
switch("prod"){case"dev":installDevToolsConsole();break;case"prod":return;default:throw new Error}

// New output (with --minify '--define:MODE="prod"')
return;

  • Emit /* @​__KEY__ */ for string literals derived from property names (#​4034)

    Property name mangling is an advanced feature that shortens certain property names for better minification (I say "advanced feature" because it's very easy to break your code with it). Sometimes you need to store a property name in a string, such as obj.get('foo') instead of obj.foo. JavaScript minifiers such as esbuild and Terser have a convention where a /* @​__KEY__ */ comment before the string makes it behave like a property name. So obj.get(/* @​__KEY__ */ 'foo') allows the contents of the string 'foo' to be shortened.

    However, esbuild sometimes itself generates string literals containing property names when transforming code, such as when lowering class fields to ES6 or when transforming TypeScript decorators. Previously esbuild didn't generate its own /* @​__KEY__ */ comments in this case, which means that minifying your code by running esbuild again on its own output wouldn't work correctly (this does not affect people that both minify and transform their code in a single step).

    With this release, esbuild will now generate /* @​__KEY__ */ comments for property names in generated string literals. To avoid lots of unnecessary output for people that don't use this advanced feature, the generated comments will only be present when the feature is active. If you want to generate the comments but not actually mangle any property names, you can use a flag that has no effect such as --reserve-props=., which tells esbuild to not mangle any property names (but still activates this feature).

  • The text loader now strips the UTF-8 BOM if present (#​3935)

    Some software (such as Notepad on Windows) can create text files that start with the three bytes 0xEF 0xBB 0xBF, which is referred to as the "byte order mark". This prefix is intended to be removed before using the text. Previously esbuild's text loader included this byte sequence in the string, which turns into a prefix of \uFEFF in a JavaScript string when decoded from UTF-8. With this release, esbuild's text loader will now remove these bytes when they occur at the start of the file.

  • Omit legal comment output files when empty (#​3670)

    Previously configuring esbuild with --legal-comment=external or --legal-comment=linked would always generate a .LEGAL.txt output file even if it was empty. Starting with this release, esbuild will now only do this if the file will be non-empty. This should result in a more organized output directory in some cases.

  • Update Go from 1.23.1 to 1.23.5 (#​4056, #​4057)

    This should have no effect on existing code as this version change does not change Go's operating system support. It may remove certain reports from vulnerability scanners that detect which version of the Go compiler esbuild uses.

    This PR was contributed by @​MikeWillCook.

  • Allow passing a port of 0 to the development server (#​3692)

    Unix sockets interpret a port of 0 to mean "pick a random unused port in the ephemeral port range". However, esbuild's default behavior when the port is not specified is to pick the first unused port starting from 8000 and upward. This is more convenient because port 8000 is typically free, so you can for example restart the development server and reload your app in the browser without needing to change the port in the URL. Since esbuild is written in Go (which does not have optional fields like JavaScript), not specifying the port in Go means it defaults to 0, so previously passing a port of 0 to esbuild caused port 8000 to be picked.

    Starting with this release, passing a port of 0 to esbuild when using the CLI or the JS API will now pass port 0 to the OS, which will pick a random ephemeral port. To make this possible, the Port option in the Go API has been changed from uint16 to int (to allow for additional sentinel values) and passing a port of -1 in Go now picks a random port. Both the CLI and JS APIs now remap an explicitly-provided port of 0 into -1 for the internal Go API.

    Another option would have been to change Port in Go from uint16 to *uint16 (Go's closest equivalent of number | undefined). However, that would make the common case of providing an explicit port in Go very awkward as Go doesn't support taking the address of integer constants. This tradeoff isn't worth it as picking a random ephemeral port is a rare use case. So the CLI and JS APIs should now match standard Unix behavior when the port is 0, but you need to use -1 instead with Go API.

  • Minification now avoids inlining constants with direct eval (#​4055)

    Direct eval can be used to introduce a new variable like this:

    const variable = false
;(function () {
  eval("var variable = true")
  console.log(variable)
})()

    Previously esbuild inlined variable here (which became false), which changed the behavior of the code. This inlining is now avoided, but please keep in mind that direct eval breaks many assumptions that JavaScript tools hold about normal code (especially when bundling) and I do not recommend using it. There are usually better alternatives that have a more localized impact on your code. You can read more about this here: https://esbuild.github.io/link/direct-eval/

capricorn86/happy-dom (happy-dom)

v16.8.1

Compare Source

👷‍♂️ Patch fixes

v16.8.0

Compare Source

🎨 Features

v16.7.3

Compare Source

👷‍♂️ Patch fixes
  • Removes space from directory name that prevents the repo to be cloned on MS Windows - By @​kleinfreund in task #​1703
chaijs/loupe (loupe)

v3.1.3

Compare Source

What's Changed

New Contributors

Full Changelog: chaijs/loupe@v3.1.2...v3.1.3

pnpm/pnpm (pnpm)

v9.15.5: pnpm 9.15.5

Compare Source

Patch Changes

  • Verify that the package name is valid when executing the publish command.
  • When running pnpm install, the preprepare and postprepare scripts of the project should be executed #​8989.
  • Quote args for scripts with shell-quote to support new lines (on POSIX only) #​8980.
  • Proxy settings should be respected, when resolving Git-hosted dependencies #​6530.
  • Replace strip-ansi with the built-in util.stripVTControlCharacters #​9009.

Platinum Sponsors

Bit Bit Figma

Gold Sponsors

Discord Prisma
u|screen JetBrains
Nx CodeRabbit
Route4Me Workleap
Canva
rollup/rollup (rollup)

v4.34.6

Compare Source

2025-02-07

Bug Fixes
  • Retain "void 0" in the output for smaller output and fewer surprises (#​5838)
Pull Requests

v4.34.5

Compare Source

2025-02-07

Bug Fixes
  • Ensure namespace reexports always include all properties of all exports (#​5837)
Pull Requests

v4.34.4

Compare Source

2025-02-05

Bug Fixes
  • Do not tree-shake properties if a rest element is used in destructuring (#​5833)
Pull Requests

v4.34.3

Compare Source

2025-02-05

Bug Fixes
  • Ensure properties of "this" are included in getters (#​5831)
Pull Requests

v4.34.2

Compare Source

2025-02-04

Bug Fixes
  • Fix an issue where not all usages of a function were properly detected (#​5827)
Pull Requests

v4.34.1

Compare Source

2025-02-03

Bug Fixes
  • Ensure throwing objects includes the entire object (#​5825)
Pull Requests

v4.34.0

Compare Source

2025-02-01

Features
  • Tree-shake unused properties in object literals (re-implements #​5420) (#​5737)
Pull Requests

Configuration

📅 Schedule: Branch creation - "* 0-3 * * 1" (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 was generated by Mend Renovate. View the repository job log.

@netlify Netlify
Copy link

netlify bot commented Jan 27, 2025 •
edited
Loading

✅ Deploy Preview for vitest-dev ready!

Name Link
🔨 Latest commit 98d2692
🔍 Latest deploy log https://app.netlify.com/sites/vitest-dev/deploys/67aaa0bf7bc6eb000821ae36
😎 Deploy Preview https://deploy-preview-7363--vitest-dev.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@renovate renovate bot force-pushed the renovate/all-minor-patch branch 3 times, most recently from 31388b3 to a586b0a Compare January 28, 2025 18:11
@renovate renovate bot changed the title chore(deps): update all non-major dependencies fix(deps): update all non-major dependencies Jan 28, 2025
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 16 times, most recently from 8ed8a98 to ccd0e67 Compare February 5, 2025 13:12
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 5 times, most recently from 5ab89c5 to a71fbc6 Compare February 7, 2025 16:49
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from a71fbc6 to e6a3bab Compare February 8, 2025 05:03
@renovate Renovate
Copy link
Contributor Author

renovate bot commented Feb 10, 2025

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.

@hi-ogawa
Copy link
Contributor

Netlify got corepack issue too, so I added a patch in d613932

hi-ogawa
hi-ogawa previously approved these changes Feb 10, 2025
View reviewed changes
hi-ogawa
hi-ogawa previously approved these changes Feb 11, 2025
View reviewed changes
@hi-ogawa hi-ogawa enabled auto-merge (squash) February 11, 2025 01:15
@hi-ogawa hi-ogawa merged commit e348bd4 into main Feb 11, 2025
12 of 13 checks passed
@hi-ogawa hi-ogawa deleted the renovate/all-minor-patch branch February 11, 2025 01:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@hi-ogawa hi-ogawa hi-ogawa approved these changes

Assignees
No one assigned
Labels
dependencies
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@hi-ogawa