chore(deps): update all non-major dependencies

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@types/node (source)	^20.11.5 -> ^20.11.16
@vitest/coverage-v8 (source)	^1.2.1 -> ^1.2.2
esbuild	^0.19.11 -> ^0.20.0
pnpm (source)	8.14.1 -> 8.15.1
rollup (source)	^4.9.5 -> ^4.9.6
vitest (source)	^1.2.1 -> ^1.2.2

---

Release Notes

vitest-dev/vitest (@​vitest/coverage-v8)

v1.2.2

Compare Source

   🐞 Bug Fixes

• coverage:
  • Remove coverage/.tmp files after run  -  by @​AriPerkkio in https://github.com/vitest-dev/vitest/issues/5008 (d53b8)
  • Don't crash when re-run removes earlier run's reports  -  by @​AriPerkkio in https://github.com/vitest-dev/vitest/issues/5022 (66898)
• expect:
  • Improve toThrow(asymmetricMatcher) failure message  -  by @​hi-ogawa in https://github.com/vitest-dev/vitest/issues/5000 (a199a)
• forks:
  • Set correct VITEST_POOL_ID  -  by @​AriPerkkio in https://github.com/vitest-dev/vitest/issues/5002 (7d0a4)
• threads:
  • Mention common work-around for the logged error  -  by @​AriPerkkio in https://github.com/vitest-dev/vitest/issues/5024 (915d6)
• typecheck:
  • Fix ignoreSourceErrors in run mode  -  by @​hi-ogawa in https://github.com/vitest-dev/vitest/issues/5044 (6dae3)
• vite-node:
  • Provide import.meta.filename and dirname  -  by @​sheremet-va in https://github.com/vitest-dev/vitest/issues/5011 (73148)
• vitest:
  • Expose getHooks & setHooks  -  by @​adriencaccia in https://github.com/vitest-dev/vitest/issues/5032 (73448)
  • Test deep dependencies change detection  -  by @​blake-newman in https://github.com/vitest-dev/vitest/issues/4934 (9c7c0)
  • Throw an error if vi.mock is exported  -  by @​sheremet-va in https://github.com/vitest-dev/vitest/issues/5034 (253df)
  • Allow useFakeTimers to fake requestIdleCallback on non browser  -  by @​hi-ogawa in https://github.com/vitest-dev/vitest/issues/5028 (a9a48)
  • Support older NodeJS with async import.meta.resolve  -  by @​AriPerkkio in https://github.com/vitest-dev/vitest/issues/5045 (cf564)
  • Don't throw an error if mocked file was already imported  -  by @​sheremet-va in https://github.com/vitest-dev/vitest/issues/5050 (fff1a)

    View changes on GitHub

evanw/esbuild (esbuild)

v0.20.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.19.0 or ~0.19.0. See npm's documentation about semver for more information.

This time there is only one breaking change, and it only matters for people using Deno. Deno tests that use esbuild will now fail unless you make the change described below.

• Work around API deprecations in Deno 1.40.x (#​3609, #​3611)

  Deno 1.40.0 was just released and introduced run-time warnings about certain APIs that esbuild uses. With this release, esbuild will work around these run-time warnings by using newer APIs if they are present and falling back to the original APIs otherwise. This should avoid the warnings without breaking compatibility with older versions of Deno.

  Unfortunately, doing this introduces a breaking change. The newer child process APIs lack a way to synchronously terminate esbuild's child process, so calling esbuild.stop() from within a Deno test is no longer sufficient to prevent Deno from failing a test that uses esbuild's API (Deno fails tests that create a child process without killing it before the test ends). To work around this, esbuild's stop() function has been changed to return a promise, and you now have to change esbuild.stop() to await esbuild.stop() in all of your Deno tests.

• Reorder implicit file extensions within node_modules (#​3341, #​3608)

  In version 0.18.0, esbuild changed the behavior of implicit file extensions within node_modules directories (i.e. in published packages) to prefer .js over .ts even when the --resolve-extensions= order prefers .ts over .js (which it does by default). However, doing that also accidentally made esbuild prefer .css over .ts, which caused problems for people that published packages containing both TypeScript and CSS in files with the same name.

  With this release, esbuild will reorder TypeScript file extensions immediately after the last JavaScript file extensions in the implicit file extension order instead of putting them at the end of the order. Specifically the default implicit file extension order is .tsx,.ts,.jsx,.js,.css,.json which used to become .jsx,.js,.css,.json,.tsx,.ts in node_modules directories. With this release it will now become .jsx,.js,.tsx,.ts,.css,.json instead.

  Why even rewrite the implicit file extension order at all? One reason is because the .js file is more likely to behave correctly than the .ts file. The behavior of the .ts file may depend on tsconfig.json and the tsconfig.json file may not even be published, or may use extends to refer to a base tsconfig.json file that wasn't published. People can get into this situation when they forget to add all .ts files to their .npmignore file before publishing to npm. Picking .js over .ts helps make it more likely that resulting bundle will behave correctly.

v0.19.12

Compare Source

• The "preserve" JSX mode now preserves JSX text verbatim (#​3605)

  The JSX specification deliberately doesn't specify how JSX text is supposed to be interpreted and there is no canonical way to interpret JSX text. Two most popular interpretations are Babel and TypeScript. Yes they are different (esbuild deliberately follows TypeScript by the way).

  Previously esbuild normalized text to the TypeScript interpretation when the "preserve" JSX mode is active. However, "preserve" should arguably reproduce the original JSX text verbatim so that whatever JSX transform runs after esbuild is free to interpret it however it wants. So with this release, esbuild will now pass JSX text through unmodified:

  // Original code
  let el =
    <a href={'/'} title='&apos;&quot;'> some text
      {foo}
        more text </a>
  
  // Old output (with --loader=jsx --jsx=preserve)
  let el = <a href="/" title={`'"`}>
    {" some text"}
    {foo}
    {"more text "}
  </a>;
  
  // New output (with --loader=jsx --jsx=preserve)
  let el = <a href={"/"} title='&apos;&quot;'> some text
      {foo}
        more text </a>;

• Allow JSX elements as JSX attribute values

  JSX has an obscure feature where you can use JSX elements in attribute position without surrounding them with {...}. It looks like this:

  let el = <div data-ab=<><a/><b/></>/>;

  I think I originally didn't implement it even though it's part of the JSX specification because it previously didn't work in TypeScript (and potentially also in Babel?). However, support for it was silently added in TypeScript 4.8 without me noticing and Babel has also since fixed their bugs regarding this feature. So I'm adding it to esbuild too now that I know it's widely supported.

  Keep in mind that there is some ongoing discussion about removing this feature from JSX. I agree that the syntax seems out of place (it does away with the elegance of "JSX is basically just XML with {...} escapes" for something arguably harder to read, which doesn't seem like a good trade-off), but it's in the specification and TypeScript and Babel both implement it so I'm going to have esbuild implement it too. However, I reserve the right to remove it from esbuild if it's ever removed from the specification in the future. So use it with caution.

• Fix a bug with TypeScript type parsing (#​3574)

  This release fixes a bug with esbuild's TypeScript parser where a conditional type containing a union type that ends with an infer type that ends with a constraint could fail to parse. This was caused by the "don't parse a conditional type" flag not getting passed through the union type parser. Here's an example of valid TypeScript code that previously failed to parse correctly:

  type InferUnion<T> = T extends { a: infer U extends number } | infer U extends number ? U : never

pnpm/pnpm (pnpm)

v8.15.1

Compare Source

Patch Changes

• Use the object-hash library instead of node-object-hash for hashing keys of side-effects cache #​7591.
• bundledDependencies should never be added to the lockfile with false as the value #​7576.

Platinum Sponsors

Gold Sponsors

Our Silver Sponsors

v8.15.0

Compare Source

Minor Changes

• When the license field does not exist in package.json but a license file exists, try to match and extract the license name #​7530.

Patch Changes

• Running pnpm update -r --latest will no longer downgrade prerelease dependencies #​7436.
• --aggregate-output should work on scripts executed from the same project #​7556.
• Prefer hard links over reflinks on Windows as they perform better #​7564.
• Reduce the length of the side-effects cache key. Instead of saving a stringified object composed from the dependency versions of the package, use the hash calculated from the said object #​7563.
• Throw an error if pnpm update --latest runs with arguments containing versions specs. For instance, pnpm update --latest foo@next is not allowed #​7567.
• Don't fail in Windows CoW if the file already exists #​7554.

Platinum Sponsors

Gold Sponsors

Our Silver Sponsors

v8.14.3

Compare Source

Patch Changes

• pnpm pack should work as expected when "prepack" modifies the manifest #​7558.

Platinum Sponsors

Gold Sponsors

Our Silver Sponsors

v8.14.2

Compare Source

Patch Changes

• Registry configuration from previous installation should not override current settings #​7507.
• pnpm dlx should not fail, when executed from package.json "scripts" 7424.
• A git-hosted dependency should not be added to the store if it failed to be built #​7407.
• pnpm publish should pack "main" file or "bin" files defined in "publishConfig" #​4195.

Platinum Sponsors

Gold Sponsors

Our Silver Sponsors

rollup/rollup (rollup)

v4.9.6

Compare Source

2024-01-21

Bug Fixes

• Detect side effects when an element that was pushed into an array is modified via the array (#​5352)

Pull Requests

• #​5337: Generate AST transformers from config (@​lukastaegert)
• #​5340: Also type-check d.ts files (@​lukastaegert)
• #​5348: chore(deps): lock file maintenance minor/patch updates (@​renovate[bot])
• #​5351: chore(deps): update dependency vite to v5.0.12 [security] (@​renovate[bot])
• #​5352: Track mutations of elements pushed into arrays (@​lukastaegert)

---

Configuration

📅 Schedule: Branch creation - "after 2am and before 3am" (UTC), Automerge - "after 1am and before 2am" (UTC).

🚦 Automerge: Enabled.

♻ 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.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (7528b13) 82.50% compared to head (9331625) 82.50%.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #113   +/-   ##
=======================================
  Coverage   82.50%   82.50%           
=======================================
  Files          10       10           
  Lines         383      383           
  Branches       32       32           
=======================================
  Hits          316      316           
  Misses         61       61           
  Partials        6        6           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.