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.

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

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

Merged
merged 1 commit into from
Apr 3, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Feb 15, 2024

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@tsconfig/node20 (source) ^20.1.2 -> ^20.1.4 age adoption passing confidence
@types/eslint (source) ^8.56.2 -> ^8.56.7 age adoption passing confidence
@types/node (source) ^20.11.18 -> ^20.12.3 age adoption passing confidence
changelogithub ^0.13.3 -> ^0.13.5 age adoption passing confidence
esbuild ^0.20.0 -> ^0.20.2 age adoption passing confidence
pnpm (source) 8.15.3 -> 8.15.6 age adoption passing confidence
rollup (source) ^4.11.0 -> ^4.14.0 age adoption passing confidence
typescript (source) ^5.3.3 -> ^5.4.3 age adoption passing confidence
typescript-eslint (source) ^7.4.0 -> ^7.5.0 age adoption passing confidence
vite (source) ^5.1.3 -> ^5.2.7 age adoption passing confidence
vitepress (source) 1.0.0-rc.42 -> 1.0.2 age adoption passing confidence
vitest (source) ^1.2.2 -> ^1.4.0 age adoption passing confidence
vue (source) ^3.4.19 -> ^3.4.21 age adoption passing confidence

Release Notes

tsconfig/bases (@​tsconfig/node20)

v20.1.4

Compare Source

v20.1.3

Compare Source

antfu/changelogithub (changelogithub)

v0.13.5

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v0.13.4

Compare Source

   🐞 Bug Fixes
    View changes on GitHub
evanw/esbuild (esbuild)

v0.20.2

Compare Source

  • Support TypeScript experimental decorators on abstract class fields (#​3684)

    With this release, you can now use TypeScript experimental decorators on abstract class fields. This was silently compiled incorrectly in esbuild 0.19.7 and below, and was an error from esbuild 0.19.8 to esbuild 0.20.1. Code such as the following should now work correctly:

    // Original code
    const log = (x: any, y: string) => console.log(y)
    abstract class Foo { @​log abstract foo: string }
    new class extends Foo { foo = '' }
    
    // Old output (with --loader=ts --tsconfig-raw={\"compilerOptions\":{\"experimentalDecorators\":true}})
    const log = (x, y) => console.log(y);
    class Foo {
    }
    new class extends Foo {
      foo = "";
    }();
    
    // New output (with --loader=ts --tsconfig-raw={\"compilerOptions\":{\"experimentalDecorators\":true}})
    const log = (x, y) => console.log(y);
    class Foo {
    }
    __decorateClass([
      log
    ], Foo.prototype, "foo", 2);
    new class extends Foo {
      foo = "";
    }();
  • JSON loader now preserves __proto__ properties (#​3700)

    Copying JSON source code into a JavaScript file will change its meaning if a JSON object contains the __proto__ key. A literal __proto__ property in a JavaScript object literal sets the prototype of the object instead of adding a property named __proto__, while a literal __proto__ property in a JSON object literal just adds a property named __proto__. With this release, esbuild will now work around this problem by converting JSON to JavaScript with a computed property key in this case:

    // Original code
    import data from 'data:application/json,{"__proto__":{"fail":true}}'
    if (Object.getPrototypeOf(data)?.fail) throw 'fail'
    
    // Old output (with --bundle)
    (() => {
      // <data:application/json,{"__proto__":{"fail":true}}>
      var json_proto_fail_true_default = { __proto__: { fail: true } };
    
      // entry.js
      if (Object.getPrototypeOf(json_proto_fail_true_default)?.fail)
        throw "fail";
    })();
    
    // New output (with --bundle)
    (() => {
      // <data:application/json,{"__proto__":{"fail":true}}>
      var json_proto_fail_true_default = { ["__proto__"]: { fail: true } };
    
      // example.mjs
      if (Object.getPrototypeOf(json_proto_fail_true_default)?.fail)
        throw "fail";
    })();
  • Improve dead code removal of switch statements (#​3659)

    With this release, esbuild will now remove switch statements in branches when minifying if they are known to never be evaluated:

    // Original code
    if (true) foo(); else switch (bar) { case 1: baz(); break }
    
    // Old output (with --minify)
    if(1)foo();else switch(bar){case 1:}
    
    // New output (with --minify)
    foo();
  • Empty enums should behave like an object literal (#​3657)

    TypeScript allows you to create an empty enum and add properties to it at run time. While people usually use an empty object literal for this instead of a TypeScript enum, esbuild's enum transform didn't anticipate this use case and generated undefined instead of {} for an empty enum. With this release, you can now use an empty enum to generate an empty object literal.

    // Original code
    enum Foo {}
    
    // Old output (with --loader=ts)
    var Foo = /* @&#8203;__PURE__ */ ((Foo2) => {
    })(Foo || {});
    
    // New output (with --loader=ts)
    var Foo = /* @&#8203;__PURE__ */ ((Foo2) => {
      return Foo2;
    })(Foo || {});
  • Handle Yarn Plug'n'Play edge case with tsconfig.json (#​3698)

    Previously a tsconfig.json file that extends another file in a package with an exports map failed to work when Yarn's Plug'n'Play resolution was active. This edge case should work now starting with this release.

  • Work around issues with Deno 1.31+ (#​3682)

    Version 0.20.0 of esbuild changed how the esbuild child process is run in esbuild's API for Deno. Previously it used Deno.run but that API is being removed in favor of Deno.Command. As part of this change, esbuild is now calling the new unref function on esbuild's long-lived child process, which is supposed to allow Deno to exit when your code has finished running even though the child process is still around (previously you had to explicitly call esbuild's stop() function to terminate the child process for Deno to be able to exit).

    However, this introduced a problem for Deno's testing API which now fails some tests that use esbuild with error: Promise resolution is still pending but the event loop has already resolved. It's unclear to me why this is happening. The call to unref was recommended by someone on the Deno core team, and calling Node's equivalent unref API has been working fine for esbuild in Node for a long time. It could be that I'm using it incorrectly, or that there's some reference counting and/or garbage collection bug in Deno's internals, or that Deno's unref just works differently than Node's unref. In any case, it's not good for Deno tests that use esbuild to be failing.

    In this release, I am removing the call to unref to fix this issue. This means that you will now have to call esbuild's stop() function to allow Deno to exit, just like you did before esbuild version 0.20.0 when this regression was introduced.

    Note: This regression wasn't caught earlier because Deno doesn't seem to fail tests that have outstanding setTimeout calls, which esbuild's test harness was using to enforce a maximum test runtime. Adding a setTimeout was allowing esbuild's Deno tests to succeed. So this regression doesn't necessarily apply to all people using tests in Deno.

v0.20.1

Compare Source

  • Fix a bug with the CSS nesting transform (#​3648)

    This release fixes a bug with the CSS nesting transform for older browsers where the generated CSS could be incorrect if a selector list contained a pseudo element followed by another selector. The bug was caused by incorrectly mutating the parent rule's selector list when filtering out pseudo elements for the child rules:

    /* Original code */
    .foo {
      &:after,
      & .bar {
        color: red;
      }
    }
    
    /* Old output (with --supported:nesting=false) */
    .foo .bar,
    .foo .bar {
      color: red;
    }
    
    /* New output (with --supported:nesting=false) */
    .foo:after,
    .foo .bar {
      color: red;
    }
  • Constant folding for JavaScript inequality operators (#​3645)

    This release introduces constant folding for the < > <= >= operators. The minifier will now replace these operators with true or false when both sides are compile-time numeric or string constants:

    // Original code
    console.log(1 < 2, '🍕' > '🧀')
    
    // Old output (with --minify)
    console.log(1<2,"🍕">"🧀");
    
    // New output (with --minify)
    console.log(!0,!1);
  • Better handling of __proto__ edge cases (#​3651)

    JavaScript object literal syntax contains a special case where a non-computed property with a key of __proto__ sets the prototype of the object. This does not apply to computed properties or to properties that use the shorthand property syntax introduced in ES6. Previously esbuild didn't correctly preserve the "sets the prototype" status of properties inside an object literal, meaning a property that sets the prototype could accidentally be transformed into one that doesn't and vice versa. This has now been fixed:

    // Original code
    function foo(__proto__) {
      return { __proto__: __proto__ } // Note: sets the prototype
    }
    function bar(__proto__, proto) {
      {
        let __proto__ = proto
        return { __proto__ } // Note: doesn't set the prototype
      }
    }
    
    // Old output
    function foo(__proto__) {
      return { __proto__ }; // Note: no longer sets the prototype (WRONG)
    }
    function bar(__proto__, proto) {
      {
        let __proto__2 = proto;
        return { __proto__: __proto__2 }; // Note: now sets the prototype (WRONG)
      }
    }
    
    // New output
    function foo(__proto__) {
      return { __proto__: __proto__ }; // Note: sets the prototype (correct)
    }
    function bar(__proto__, proto) {
      {
        let __proto__2 = proto;
        return { ["__proto__"]: __proto__2 }; // Note: doesn't set the prototype (correct)
      }
    }
  • Fix cross-platform non-determinism with CSS color space transformations (#​3650)

    The Go compiler takes advantage of "fused multiply and add" (FMA) instructions on certain processors which do the operation x*y + z without intermediate rounding. This causes esbuild's CSS color space math to differ on different processors (currently ppc64le and s390x), which breaks esbuild's guarantee of deterministic output. To avoid this, esbuild's color space math now inserts a float64() cast around every single math operation. This tells the Go compiler not to use the FMA optimization.

  • Fix a crash when resolving a path from a directory that doesn't exist (#​3634)

    This release fixes a regression where esbuild could crash when resolving an absolute path if the source directory for the path resolution operation doesn't exist. While this situation doesn't normally come up, it could come up when running esbuild concurrently with another operation that mutates the file system as esbuild is doing a build (such as using git to switch branches). The underlying problem was a regression that was introduced in version 0.18.0.

pnpm/pnpm (pnpm)

v8.15.6

Compare Source

Patch Changes

  • The exit code of the child process should be preserved on pnpm run #​7817.
  • When sorting packages in a workspace, take into account workspace dependencies specified as peerDependencies #​7813.
  • Add --ignore-scripts argument to prune command #​7836.

Platinum Sponsors

Gold Sponsors

Silver Sponsors

v8.15.5

Compare Source

v8.15.4

Compare Source

rollup/rollup (rollup)

v4.14.0

Compare Source

2024-04-03

Features
  • Display error causes in Rollup CLI (#​5422)
  • Add basic support for explicit resource management via "using" and "await using" (#​5423)
Pull Requests

v4.13.2

Compare Source

2024-03-28

Bug Fixes
  • Ensure accessing module info is cached after the build phase for improved performance (#​5438)
  • Support powerpc64le CPUs (#​5350)
Pull Requests

v4.13.1

Compare Source

2024-03-27

Bug Fixes
  • Add new linux-s390x-gnu native binary package (#​5346)
Pull Requests

v4.13.0

Compare Source

2024-03-12

Features
  • Ensure that the location of parse errors and other logs is encoded in the error message as well (#​5424)
Pull Requests

v4.12.1

Compare Source

2024-03-06

Bug Fixes
  • Escape special characters in file references (#​5404)
Pull Requests

v4.12.0

Compare Source

2024-02-16

Features
  • Improve raw bundling performance by 10-15% when not using the cache or plugins that return an AST (#​5391)
Pull Requests
Microsoft/TypeScript (typescript)

v5.4.3: TypeScript 5.4.3

Compare Source

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

Downloads are available on:

v5.4.2: TypeScript 5.4

Compare Source

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

Downloads are available on:

typescript-eslint/typescript-eslint (typescript-eslint)

v7.5.0

Compare Source

🩹 Fixes
  • typescript-eslint: improve support for legacy configs
❤️ Thank You
  • Brad Zacher
  • Kim Sang Du
  • Mark de Dios
  • Naru
  • YeonJuan

You can read about our versioning strategy and releases on our website.

vitejs/vite (vite)

v5.2.7

Compare Source

v5.2.6

Compare Source

v5.2.5

Compare Source

v5.2.4

v5.2.3

v5.2.2

v5.2.1

v5.2.0

v5.1.7

Compare Source

Please refer to CHANGELOG.md for details.

v5.1.6

Compare Source

v5.1.5

Compare Source

v5.1.4

Compare Source

vuejs/vitepress (vitepress)

v1.0.2

Compare Source

Bug Fixes
  • theme: text containing html not showing properly in mobile nav menu (3c8b4c7)

v1.0.1

Compare Source

Bug Fixes
  • build: vendor vue-demi to avoid resolution issues with yarn berry (#​3680) (5d3cb96)

v1.0.0

Compare Source

Bug Fixes

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), 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.

Copy link

vercel bot commented Feb 15, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
utilix-docs ✅ Ready (Inspect) Visit Preview 💬 Add feedback Apr 3, 2024 6:11am

@renovate renovate bot requested a review from Waleed-KH as a code owner February 15, 2024 18:48
@renovate renovate bot changed the title chore(deps): update dependency @types/node to v20.11.19 chore(deps): update all non-major dependencies Feb 16, 2024
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from b5ba829 to 68c11b7 Compare March 24, 2024 11:20
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 68c11b7 to 80ab203 Compare March 24, 2024 13:49
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 80ab203 to 6fdd149 Compare March 27, 2024 08:42
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 6fdd149 to 3597126 Compare March 27, 2024 11:16
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 3597126 to 3a1a0a0 Compare March 28, 2024 17:35
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 3a1a0a0 to 62c490f Compare March 29, 2024 11:36
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 62c490f to c9411ff Compare March 30, 2024 07:19
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from c9411ff to ee17466 Compare April 1, 2024 12:32
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from ee17466 to 5e9cf5b Compare April 1, 2024 15:46
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 5e9cf5b to 1763dcd Compare April 1, 2024 21:37
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 1763dcd to deb17bc Compare April 2, 2024 13:38
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from deb17bc to 7823c53 Compare April 2, 2024 22:43
@Waleed-KH Waleed-KH merged commit c32ca51 into main Apr 3, 2024
6 checks passed
@renovate renovate bot deleted the renovate/all-minor-patch branch April 3, 2024 10:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant