Skip to content

chore(deps): lock file maintenance npm packages #124

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
Merged
merged 1 commit into from
May 5, 2025
Merged

chore(deps): lock file maintenance npm packages #124

merged 1 commit into from
May 5, 2025

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented May 5, 2025 •
edited
Loading

This PR contains the following updates:

Package Type Update Change Age Adoption Passing Confidence
lockFileMaintenance All locks refreshed
@nestjs/common (source) devDependencies minor 11.0.20 -> 11.1.0 age adoption passing confidence
@nestjs/core (source) devDependencies minor 11.0.20 -> 11.1.0 age adoption passing confidence
@nestjs/platform-express (source) devDependencies minor 11.0.20 -> 11.1.0 age adoption passing confidence
@swc/core (source) devDependencies patch 1.11.21 -> 1.11.24 age adoption passing confidence
@types/node (source) devDependencies minor 22.14.1 -> 22.15.3 age adoption passing confidence
@types/react-dom (source) devDependencies patch 19.1.2 -> 19.1.3 age adoption passing confidence
ava (source) devDependencies minor 6.2.0 -> 6.3.0 age adoption passing confidence
file-type dependencies minor 20.4.1 -> 20.5.0 age adoption passing confidence
core-js (source) devDependencies minor 3.41.0 -> 3.42.0 age adoption passing confidence
esbuild devDependencies patch 0.25.2 -> 0.25.3 age adoption passing confidence
tsx (source) devDependencies patch 4.19.3 -> 4.19.4 age adoption passing confidence
oxlint (source) devDependencies patch 0.16.7 -> 0.16.9 age adoption passing confidence

🔧 This Pull Request updates lock files to use the latest dependency versions.

Release Notes

nestjs/nest (@​nestjs/common)

v11.1.0

Compare Source

v11.0.21

Compare Source

nestjs/nest (@​nestjs/core)

v11.1.0

Compare Source

v11.1.0 (2025-04-23)

Enhancements
Committers: 1

v11.0.21

Compare Source

swc-project/swc (@​swc/core)

v1.11.24

Compare Source

v1.11.22

Compare Source

Bug Fixes
Features

  • (bindings/core) Enhance existing parse function to accept both string and buffer types(#​10371) (c9a2afc)

  • (css/prefixer) Fix default implementation (#​10351) (34f4e41)

Miscellaneous Tasks
Performance
Refactor
Testing
avajs/ava (ava)

v6.3.0

Compare Source

What's Changed

New Contributors

Full Changelog: avajs/ava@v6.2.0...v6.3.0

sindresorhus/file-type (file-type)

v20.5.0

Compare Source

  • Add support Office PowerPoint 2007 (macro-enabled) slide show (#​747) f1b4c7a
zloirock/core-js (core-js)

v3.42.0

Compare Source

  • Changes v3.41.0...v3.42.0 (142 commits)
  • Map upsert proposal:
    • Moved to stage 2.7, April 2025 TC39 meeting
    • Validation order of WeakMap.prototype.getOrInsertComputed updated following tc39/proposal-upsert#79
    • Built-ins:
      • Map.prototype.getOrInsert
      • Map.prototype.getOrInsertComputed
      • WeakMap.prototype.getOrInsert
      • WeakMap.prototype.getOrInsertComputed
  • Don't call well-known Symbol methods for RegExp on primitive values following tc39/ecma262#3009:
    • For avoid performance regression, temporarily, only in own core-js implementations
    • Built-ins:
      • String.prototype.matchAll
      • String.prototype.match
      • String.prototype.replaceAll
      • String.prototype.replace
      • String.prototype.search
      • String.prototype.split
  • Added workaround for the Uint8Array.prototype.setFromBase64 bug in some of Linux builds of WebKit
  • Implemented early-error iterator closing following tc39/ecma262#3467, including fix of a WebKit bug, in the following methods:
    • Iterator.prototype.drop
    • Iterator.prototype.every
    • Iterator.prototype.filter
    • Iterator.prototype.find
    • Iterator.prototype.flatMap
    • Iterator.prototype.forEach
    • Iterator.prototype.map
    • Iterator.prototype.reduce
    • Iterator.prototype.some
    • Iterator.prototype.take
  • Fixed missing forced replacement of AsyncIterator helpers
  • Added closing of sync iterator when async wrapper yields a rejection following tc39/ecma262#2600. Affected methods:
  • Added detection for throwing on undefined initial parameter in Iterator.prototype.reduce (see WebKit bug)
  • core-js-compat and core-js-builder API:
    • Added 'intersect' support for targets.esmodules (Babel 7 behavior)
    • Fixed handling of targets.esmodules: true (Babel 7 behavior)
  • Compat data improvements:
evanw/esbuild (esbuild)

v0.25.3

Compare Source

  • Fix lowered async arrow functions before super() (#​4141, #​4142)

    This change makes it possible to call an async arrow function in a constructor before calling super() when targeting environments without async support, as long as the function body doesn't reference this. Here's an example (notice the change from this to null):

    // Original code
class Foo extends Object {
  constructor() {
    (async () => await foo())()
    super()
  }
}

// Old output (with --target=es2016)
class Foo extends Object {
  constructor() {
    (() => __async(this, null, function* () {
      return yield foo();
    }))();
    super();
  }
}

// New output (with --target=es2016)
class Foo extends Object {
  constructor() {
    (() => __async(null, null, function* () {
      return yield foo();
    }))();
    super();
  }
}

    Some background: Arrow functions with the async keyword are transformed into generator functions for older language targets such as --target=es2016. Since arrow functions capture this, the generated code forwards this into the body of the generator function. However, JavaScript class syntax forbids using this in a constructor before calling super(), and this forwarding was problematic since previously happened even when the function body doesn't use this. Starting with this release, esbuild will now only forward this if it's used within the function body.

    This fix was contributed by @​magic-akari.

  • Fix memory leak with --watch=true (#​4131, #​4132)

    This release fixes a memory leak with esbuild when --watch=true is used instead of --watch. Previously using --watch=true caused esbuild to continue to use more and more memory for every rebuild, but --watch=true should now behave like --watch and not leak memory.

    This bug happened because esbuild disables the garbage collector when it's not run as a long-lived process for extra speed, but esbuild's checks for which arguments cause esbuild to be a long-lived process weren't updated for the new --watch=true style of boolean command-line flags. This has been an issue since this boolean flag syntax was added in version 0.14.24 in 2022. These checks are unfortunately separate from the regular argument parser because of how esbuild's internals are organized (the command-line interface is exposed as a separate Go API so you can build your own custom esbuild CLI).

    This fix was contributed by @​mxschmitt.

  • More concise output for repeated legal comments (#​4139)

    Some libraries have many files and also use the same legal comment text in all files. Previously esbuild would copy each legal comment to the output file. Starting with this release, legal comments duplicated across separate files will now be grouped in the output file by unique comment content.

  • Allow a custom host with the development server (#​4110)

    With this release, you can now use a custom non-IP host with esbuild's local development server (either with --serve= for the CLI or with the serve() call for the API). This was previously possible, but was intentionally broken in version 0.25.0 to fix a security issue. This change adds the functionality back except that it's now opt-in and only for a single domain name that you provide.

    For example, if you add a mapping in your /etc/hosts file from local.example.com to 127.0.0.1 and then use esbuild --serve=local.example.com:8000, you will now be able to visit http://local.example.com:8000/ in your browser and successfully connect to esbuild's development server (doing that would previously have been blocked by the browser). This should also work with HTTPS if it's enabled (see esbuild's documentation for how to do that).

  • Add a limit to CSS nesting expansion (#​4114)

    With this release, esbuild will now fail with an error if there is too much CSS nesting expansion. This can happen when nested CSS is converted to CSS without nesting for older browsers as expanding CSS nesting is inherently exponential due to the resulting combinatorial explosion. The expansion limit is currently hard-coded and cannot be changed, but is extremely unlikely to trigger for real code. It exists to prevent esbuild from using too much time and/or memory. Here's an example:

    a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{color:red}}}}}}}}}}}}}}}}}}}}

    Previously, transforming this file with --target=safari1 took 5 seconds and generated 40mb of CSS. Trying to do that will now generate the following error instead:

    ✘ [ERROR] CSS nesting is causing too much expansion

    example.css:1:60:
      1 │ a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{color:red}}}}}}}}}}}}}}}}}}}}
        ╵                                                             ^

  CSS nesting expansion was terminated because a rule was generated with 65536 selectors. This limit
  exists to prevent esbuild from using too much time and/or memory. Please change your CSS to use
  fewer levels of nesting.

  • Fix path resolution edge case (#​4144)

    This fixes an edge case where esbuild's path resolution algorithm could deviate from node's path resolution algorithm. It involves a confusing situation where a directory shares the same file name as a file (but without the file extension). See the linked issue for specific details. This appears to be a case where esbuild is correctly following node's published resolution algorithm but where node itself is doing something different. Specifically the step LOAD_AS_FILE appears to be skipped when the input ends with ... This release changes esbuild's behavior for this edge case to match node's behavior.

  • Update Go from 1.23.7 to 1.23.8 (#​4133, #​4134)

    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, such as for CVE-2025-22871.

    As a reminder, esbuild's development server is intended for development, not for production, so I do not consider most networking-related vulnerabilities in Go to be vulnerabilities in esbuild. Please do not use esbuild's development server in production.

privatenumber/tsx (tsx)

v4.19.4

Compare Source

oxc-project/oxc (oxlint)

v0.16.9: oxlint v0.16.9

Compare Source

[0.16.9] - 2025-05-03

Features
Bug Fixes
  • 4ee95ec editor: Activate extension when astro files are opened too (#​10725) (Sysix)
  • 46665bd langage_server: Fix initialize nested configs (#​10698) (Sysix)
  • eb3f37c language_server: On configuration change, send updated diagnostics to the client (#​10764) (Sysix)
  • 8c499c6 linter: Fix panic when doing code gen on regexp (#​10769) (camc314)
  • 8e99abf linter: Fix grammer in no unused vars diagnostic msg (#​10770) (camc314)
  • b38338a linter: Make require post message target origin a fixer a suggestion (#​10754) (camc314)
  • 48c542d linter: Skip linting vue <script> where lang is not js / ts (#​10740) (Boshen)
  • c9575f6 linter: Fix false positive in react/exhaustive deps (#​10727) (camc314)
  • d8d8f64 linter: Shorten span of promise/prefer-await-to-then (#​10717) (camc314)
  • a88e349 linter: Mark isNan and isFinite as dangerous fixes in unicorn/prefer-number-properties (#​10706) (Sysix)
  • f4ab05f linter: Panic in unicorn/no-useless-spread (#​10715) (camc314)
  • 06f1717 linter: False positive in no unused vars when importing value used as type (#​10690) (camc314)
  • 746b318 linter: False positive in typescript/explicit-function-return-type with satisfies (#​10668) (camc314)
  • cce1043 linter: False positive in typescript/explicit-function-return-type (#​10667) (camc314)
  • c89da93 linter: False positive in eslint/curly on windows (#​10671) (camc314)
  • 374e19e linter: False positive in react/jsx-curly-brace-presence (#​10663) (camc314)
  • e7c2b32 linter: Move consistent-assert to pedantic (#​10665) (camc314)
  • 344ef88 linter: False positive in eslint/no-unused-vars when calling inside sequence expression (#​10646) (Ulrich Stark)
  • 98bcd5f lsp: Incorrect quick fix offset in vue files (#​10742) (camc314)
Documentation
Refactor
Testing

v0.16.8: oxlint v0.16.8

Compare Source

[0.16.8] - 2025-04-27

Features
  • 53394a7 linter: Add auto-fix for eslint/require-await (#​10624) (yefan)
  • 6908bc3 linter: Add autofix for react/self-closing-comp (#​10512) (x6eull)
  • e228840 parser: Fast forward lexer to EOF if errors are encountered (#​10579) (Boshen)
Bug Fixes
  • 966fb03 editor: Fix memory leaks when server or watchers restarted (#​10628) (Sysix)
  • f3eac51 language_server: Fix max integer values for range position (#​10623) (Alexander S.)
  • d309e07 language_server: Fix panics when paths contains specials characters like [ or ] (#​10622) (Alexander S.)
  • 91ce77a language_server: Temporary ignore tests that panic on Windows (#​10583) (Yuji Sugiura)
  • 723b4c6 linter: Cross_module of LintService not being enabled despite enabled import plugin (#​10597) (Ulrich Stark)
  • 39adefe linter: Handle re-exporting of type correctly in import/no-cycle (#​10606) (Ulrich Stark)
  • e67901b linter: Incorrect fix for prefer start ends with (#​10533) (camc314)
  • 7c85ae7 linter/no-empty-function: Support 'allow' option (#​10605) (Don Isaac)
  • 9a02066 oxlint: Current dir as arg (#​9382) (Ben Jones)
  • a9785e3 parser,linter: Consider typescript declarations for named exports (#​10532) (Ulrich Stark)
Performance
  • 3c27d0d editor: Avoid sending workspace/didChangeConfiguration request when the server needs a restarts (#​10550) (Sysix)
Refactor
  • e903ba2 editor: Split Config to VSCodeConfig and WorkspaceConfig (#​10572) (Sysix)
  • f6c6969 language_server: Make linter independent of Backend (#​10497) (Sysix)
  • db05a15 language_server: Do not request for worspace configuration when the client does not support it (#​10507) (Sysix)
  • 9f9e0e5 language_server: Move code actions into own file (#​10479) (Sysix)
Testing

Configuration

📅 Schedule: Branch creation - "before 2pm on monday" in timezone Asia/Shanghai, Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, 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.

@renovate renovate bot force-pushed the renovate/npm-packages branch 2 times, most recently from 6d002fc to 6a500e6 Compare May 5, 2025 03:14
@renovate renovate bot force-pushed the renovate/npm-packages branch from 6a500e6 to 9e43b85 Compare May 5, 2025 03:36
@Brooooooklyn Brooooooklyn merged commit f36fedd into main May 5, 2025
56 checks passed
@Brooooooklyn Brooooooklyn deleted the renovate/npm-packages branch May 5, 2025 07:07
@renovate renovate bot mentioned this pull request Aug 13, 2025
Open
1 task
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@Brooooooklyn Brooooooklyn Brooooooklyn approved these changes

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

Successfully merging this pull request may close these issues.
1 participant
@Brooooooklyn