chore(deps): update all non-major dependencies

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@vitest/ui	0.25.8 -> 0.26.2
esbuild	0.16.9 -> 0.16.10
pnpm (source)	7.18.2 -> 7.20.0
vitest	0.25.8 -> 0.26.2

---

Release Notes

vitest-dev/vitest

v0.26.2

Compare Source

   🚀 Features

• Project name  -  by @​antfu (84f98)

   🐞 Bug Fixes

• Improve "isInternaRequest" check  -  by @​sheremet-va in https://github.com/vitest-dev/vitest/issues/2541 (2bb9a)
• Use correct word when printing "long-running" warning  -  by @​simon-abbott in https://github.com/vitest-dev/vitest/issues/2546 (8dc1c)
• Pass down diff options  -  by @​sheremet-va in https://github.com/vitest-dev/vitest/issues/2545 (98c94)
• cli: Respect inline config dir  -  by @​antfu in https://github.com/vitest-dev/vitest/issues/2550 (f6b59)

    View changes on GitHub

v0.26.1

Compare Source

   🚀 Features

• Add more options to configure diff output  -  by @​sheremet-va and @​dammy001 in https://github.com/vitest-dev/vitest/issues/2522 (7ae14)

   🐞 Bug Fixes

• Don't resolve builtin Node modules  -  by @​sheremet-va in https://github.com/vitest-dev/vitest/issues/2538 (1cbc2)

    View changes on GitHub

v0.26.0

Compare Source

   🚨 Breaking Changes

• vite-node: Rewrite how vite-node resolves id  -  by @​sheremet-va in https://github.com/vitest-dev/vitest/issues/2463 (58ee8)
• Correctly interop nested default for external and inlined modules  -  by @​sheremet-va in https://github.com/vitest-dev/vitest/issues/2512 (084e9)
  • If your environment is node, Vitest will not resolve invalid named exports (exports that are on "default" property will not magically appear as named exports), unless deps.interopDefault is enabled, or dependency is in deps.inline. This change doesn't affect jsdom, happy-dom or edge environments.
• web-worker: Make web-worker implementation more compatible with spec  -  by @​sheremet-va in https://github.com/vitest-dev/vitest/issues/2431 (c3a63)
  • Messages are now cloned with structuredClone, if it's available, or fallbacks to a polyfill.
  • Added support for SharedWorker

   🚀 Features

• Introduce a native way to set env and globals  -  by @​sheremet-va in https://github.com/vitest-dev/vitest/issues/2515 (b114d)
• Add html reporter based on Vitest UI  -  by @​poyoho and @​sheremet-va in https://github.com/vitest-dev/vitest/issues/2444 (b8f34)
  • If you have @vitest/ui installed, you can now use 'html' reporter to get a beautiful UI to view your test results, inspect module graph and read log messages.

   🐞 Bug Fixes

• Allow assigning new hotContext  -  by @​cometkim in https://github.com/vitest-dev/vitest/issues/2524 (b4c43)

    View changes on GitHub

evanw/esbuild

v0.16.10

Compare Source

• Change the default "legal comment" behavior again (#​2745)

  The legal comments feature automatically gathers comments containing @license or @preserve and puts the comments somewhere (either in the generated code or in a separate file). This behavior used to be on by default but was disabled by default in version 0.16.0 because automatically inserting comments is potentially confusing and misleading. These comments can appear to be assigning the copyright of your code to another entity. And this behavior can be especially problematic if it happens automatically by default since you may not even be aware of it happening. For example, if you bundle the TypeScript compiler the preserving legal comments means your source code would contain this comment, which appears to be assigning the copyright of all of your code to Microsoft:

  /*! *****************************************************************************
  Copyright (c) Microsoft Corporation. All rights reserved.
  Licensed under the Apache License, Version 2.0 (the "License"); you may not use
  this file except in compliance with the License. You may obtain a copy of the
  License at http://www.apache.org/licenses/LICENSE-2.0
  
  THIS CODE IS PROVIDED ON AN *AS IS* BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
  KIND, EITHER EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION ANY IMPLIED
  WARRANTIES OR CONDITIONS OF TITLE, FITNESS FOR A PARTICULAR PURPOSE,
  MERCHANTABLITY OR NON-INFRINGEMENT.
  
  See the Apache Version 2.0 License for specific language governing permissions
  and limitations under the License.
  ***************************************************************************** */

  However, people have asked for this feature to be re-enabled by default. To resolve the confusion about what these comments are applying to, esbuild's default behavior will now be to attempt to describe which package the comments are coming from. So while this feature has been re-enabled by default, the output will now look something like this instead:

  /*! Bundled license information:
  
  typescript/lib/typescript.js:
    (*! *****************************************************************************
    Copyright (c) Microsoft Corporation. All rights reserved.
    Licensed under the Apache License, Version 2.0 (the "License"); you may not use
    this file except in compliance with the License. You may obtain a copy of the
    License at http://www.apache.org/licenses/LICENSE-2.0
  
    THIS CODE IS PROVIDED ON AN *AS IS* BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
    KIND, EITHER EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION ANY IMPLIED
    WARRANTIES OR CONDITIONS OF TITLE, FITNESS FOR A PARTICULAR PURPOSE,
    MERCHANTABLITY OR NON-INFRINGEMENT.
  
    See the Apache Version 2.0 License for specific language governing permissions
    and limitations under the License.
    ***************************************************************************** *)
  */

  Note that you can still customize this behavior with the --legal-comments= flag. For example, you can use --legal-comments=none to turn this off, or you can use --legal-comments=linked to put these comments in a separate .LEGAL.txt file instead.

• Enable external legal comments with the transform API (#​2390)

  Previously esbuild's transform API only supported none, inline, or eof legal comments. With this release, external legal comments are now also supported with the transform API. This only applies to the JS and Go APIs, not to the CLI, and looks like this:

  • JS:

    const { code, legalComments } = await esbuild.transform(input, {
      legalComments: 'external',
    })

  • Go:

    result := api.Transform(input, api.TransformOptions{
      LegalComments: api.LegalCommentsEndOfFile,
    })
    code := result.Code
    legalComments := result.LegalComments

• Fix duplicate function declaration edge cases (#​2757)

  The change in the previous release to forbid duplicate function declarations in certain cases accidentally forbid some edge cases that should have been allowed. Specifically duplicate function declarations are forbidden in nested blocks in strict mode and at the top level of modules, but are allowed when they are declared at the top level of function bodies. This release fixes the regression by re-allowing the last case.

• Allow package subpaths with alias (#​2715)

  Previously the names passed to the alias feature had to be the name of a package (with or without a package scope). With this release, you can now also use the alias feature with package subpaths. So for example you can now create an alias that substitutes @org/pkg/lib with something else.

pnpm/pnpm

v7.20.0

Compare Source

Minor Changes

• pnpm gets its own implementation of the following commands:

  • pnpm config get
  • pnpm config set
  • pnpm config delete
  • pnpm config list

  In previous versions these commands were passing through to npm CLI.

  PR: #​5829
  Related issue: #​5621

• Add show alias to pnpm view #​5835.

• pnpm reads settings from its own global configuration file at $XDG_CONFIG_HOME/pnpm/rc #​5829.

• Add the 'description'-field to the licenses output #​5836.

Patch Changes

• pnpm rebuild should not fail if node_modules was created by pnpm version 7.18 or older #​5815.
• pnpm env should print help.
• Run the prepublish scripts of packages installed from Git #​5826.
• pnpm rebuild should print a better error message when a hoisted dependency is not found #​5815.

Our Gold Sponsors

Our Silver Sponsors

v7.19.0

Compare Source

Minor Changes

• New setting supported in the package.json that is in the root of the workspace: pnpm.requiredScripts. Scripts listed in this array will be required in each project of the worksapce. Otherwise, pnpm -r run <script name> will fail #​5569.
• When the hoisted node linker is used, preserve node_modules directories when linking new dependencies. This improves performance, when installing in a project that already has a node_modules directory #​5795.
• When the hoisted node linker is used, pnpm should not build the same package multiple times during installation. If a package is present at multipe locations because hoisting could not hoist them to a single directory, then the package should only built in one of the locations and copied to the rest #​5814.

Patch Changes

• pnpm rebuild should work in projects that use the hoisted node linker #​5560.
• pnpm patch should print instructions about how to commit the changes #​5809.
• Allow the -S flag in command shims pnpm/cmd-shim#​42.
• Don't relink injected directories if they were not built #​5792.

Our Gold Sponsors

Our Silver Sponsors

---

Configuration

📅 Schedule: Branch creation - "before 3am 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.

[bolt-new-by-stackblitz]

Run & review this pull request in StackBlitz Codeflow.