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

Merged
merged 1 commit into from
Feb 10, 2024
Merged

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

merged 1 commit into from
Feb 10, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Nov 27, 2023 •
edited
Loading

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@faker-js/faker ^8.3.1 -> ^8.4.1 age adoption passing confidence
@sxzz/eslint-config ^3.7.4 -> ^3.7.6 age adoption passing confidence
@types/node (source) ^20.9.2 -> ^20.11.17 age adoption passing confidence
@vitest/ui (source) ^1.0.4 -> ^1.2.2 age adoption passing confidence
bumpp ^9.2.0 -> ^9.3.0 age adoption passing confidence
esbuild ^0.19.6 -> ^0.20.0 age adoption passing confidence
eslint (source) ^8.54.0 -> ^8.56.0 age adoption passing confidence
ky ^1.1.3 -> ^1.2.0 age adoption passing confidence
pnpm (source) 8.10.5 -> 8.15.1 age adoption passing confidence
rollup (source) ^4.5.0 -> ^4.10.0 age adoption passing confidence
sharp (source, changelog) ^0.32.6 -> ^0.33.2 age adoption passing confidence
tsup (source) ^8.0.0 -> ^8.0.1 age adoption passing confidence
tsx ^4.1.4 -> ^4.7.1 age adoption passing confidence
typedoc (source) ^0.25.3 -> ^0.25.8 age adoption passing confidence
typescript (source) ^5.2.2 -> ^5.3.3 age adoption passing confidence
vitest (source) ^1.0.4 -> ^1.2.2 age adoption passing confidence

Release Notes

faker-js/faker (@​faker-js/faker)

v8.4.1

Compare Source

  • JSDocs improvements

v8.4.0

Compare Source

Features
Bug Fixes
8.3.1 (2023-11-14)
Bug Fixes
  • remove [@internal](https://github.com/internal) from module parent classes (#​2548) (77f54ad)
sxzz/eslint-config (@​sxzz/eslint-config)

v3.7.6

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v3.7.5

Compare Source

   🐞 Bug Fixes
    View changes on GitHub
vitest-dev/vitest (@​vitest/ui)

v1.2.2

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v1.2.1

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v1.2.0

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v1.1.3

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v1.1.2

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v1.1.1

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v1.1.0

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub
antfu/bumpp (bumpp)

v9.3.0

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v9.2.1

Compare Source

   🚀 Features
    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

v0.19.11

Compare Source

  • Fix TypeScript-specific class transform edge case (#​3559)

    The previous release introduced an optimization that avoided transforming super() in the class constructor for TypeScript code compiled with useDefineForClassFields set to false if all class instance fields have no initializers. The rationale was that in this case, all class instance fields are omitted in the output so no changes to the constructor are needed. However, if all of this is the case and there are #private instance fields with initializers, those private instance field initializers were still being moved into the constructor. This was problematic because they were being inserted before the call to super() (since super() is now no longer transformed in that case). This release introduces an additional optimization that avoids moving the private instance field initializers into the constructor in this edge case, which generates smaller code, matches the TypeScript compiler's output more closely, and avoids this bug:

    // Original code
class Foo extends Bar {
  #private = 1;
  public: any;
  constructor() {
    super();
  }
}

// Old output (with esbuild v0.19.9)
class Foo extends Bar {
  constructor() {
    super();
    this.#private = 1;
  }
  #private;
}

// Old output (with esbuild v0.19.10)
class Foo extends Bar {
  constructor() {
    this.#private = 1;
    super();
  }
  #private;
}

// New output
class Foo extends Bar {
  #private = 1;
  constructor() {
    super();
  }
}

  • Minifier: allow reording a primitive past a side-effect (#​3568)

    The minifier previously allowed reordering a side-effect past a primitive, but didn't handle the case of reordering a primitive past a side-effect. This additional case is now handled:

    // Original code
function f() {
  let x = false;
  let y = x;
  const boolean = y;
  let frag = $.template(`<p contenteditable="${boolean}">hello world</p>`);
  return frag;
}

// Old output (with --minify)
function f(){const e=!1;return $.template(`<p contenteditable="${e}">hello world</p>`)}

// New output (with --minify)
function f(){return $.template('<p contenteditable="false">hello world</p>')}

  • Minifier: consider properties named using known Symbol instances to be side-effect free (#​3561)

    Many things in JavaScript can have side effects including property accesses and ToString operations, so using a symbol such as Symbol.iterator as a computed property name is not obviously side-effect free. This release adds a special case for known Symbol instances so that they are considered side-effect free when used as property names. For example, this class declaration will now be considered side-effect free:

    class Foo {
  *[Symbol.iterator]() {
  }
}

  • Provide the stop() API in node to exit esbuild's child process (#​3558)

    You can now call stop() in esbuild's node API to exit esbuild's child process to reclaim the resources used. It only makes sense to do this for a long-lived node process when you know you will no longer be making any more esbuild API calls. It is not necessary to call this to allow node to exit, and it's advantageous to not call this in between calls to esbuild's API as sharing a single long-lived esbuild child process is more efficient than re-creating a new esbuild child process for every API call. This API call used to exist but was removed in version 0.9.0. This release adds it back due to a user request.

[v0.19.10](https://github.com/evanw/esbuil

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.

@stackblitz StackBlitz
Copy link

stackblitz bot commented Nov 27, 2023

Review PR in StackBlitz Codeflow Run & review this pull request in StackBlitz Codeflow.

@vercel Vercel
Copy link

vercel bot commented Nov 27, 2023 •
edited
Loading

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

Name Status Preview Comments Updated (UTC)
jike-sdk ✅ Ready (Inspect) Visit Preview 💬 Add feedback Feb 10, 2024 6:27am

@renovate renovate bot force-pushed the renovate/all-minor-patch branch from c99796d to b2c237b Compare November 27, 2023 14:37
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from b2c237b to 01047d6 Compare November 28, 2023 00:56
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 01047d6 to 13f28e5 Compare November 29, 2023 17:04
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 13f28e5 to 5d7d58f Compare November 29, 2023 23:15
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 5d7d58f to 9ca56c7 Compare November 30, 2023 05:04
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 9ca56c7 to a367499 Compare November 30, 2023 08:05
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from a367499 to 287eaf3 Compare November 30, 2023 16:42
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 287eaf3 to d84089f Compare December 1, 2023 23:24
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from d84089f to 4d63c6b Compare December 2, 2023 09:04
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 4d63c6b to 678155e Compare December 3, 2023 19:16
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 678155e to 7ec7453 Compare December 4, 2023 18:41
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 7ec7453 to d1f0c0d Compare December 6, 2023 19:59
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from d1f0c0d to 99cc2e7 Compare December 7, 2023 10:00
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 48f4d28 to e639bf6 Compare January 26, 2024 16:46
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from e639bf6 to 8d95c7a Compare January 27, 2024 17:09
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 8d95c7a to f23037f Compare January 28, 2024 16:11
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from f23037f to 3ab8914 Compare January 29, 2024 00:39
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 3ab8914 to d0f719d Compare January 29, 2024 21:50
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from d0f719d to 7ff8e3b Compare January 30, 2024 22:59
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 7ff8e3b to fd964a2 Compare January 31, 2024 01:59
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from fd964a2 to 2ede3c4 Compare January 31, 2024 22:47
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 2ede3c4 to f8b6147 Compare February 2, 2024 12:30
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from f8b6147 to b6e1d23 Compare February 8, 2024 19:46
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from b6e1d23 to d93b06c Compare February 8, 2024 21:04
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from d93b06c to d024666 Compare February 10, 2024 02:00
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from d024666 to 1d65763 Compare February 10, 2024 06:27
@sxzz sxzz merged commit f21c9ea into main Feb 10, 2024
5 checks passed
@sxzz sxzz deleted the renovate/all-minor-patch branch February 10, 2024 12:23
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.
1 participant
@sxzz