Skip to content

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

Merged
Brooooooklyn merged 1 commit intomainfrom
renovate/npm-packages
Apr 23, 2025
Merged

chore(deps): lock file maintenance npm packages#111
Brooooooklyn merged 1 commit intomainfrom
renovate/npm-packages

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Apr 21, 2025 •
edited
Loading

This PR contains the following updates:

Package Type Update Change Age Adoption Passing Confidence
lockFileMaintenance All locks refreshed
@napi-rs/cli devDependencies patch 3.0.0-alpha.77 -> 3.0.0-alpha.78 age adoption passing confidence
@napi-rs/wasm-runtime (source) devDependencies patch 0.2.8 -> 0.2.9 age adoption passing confidence
@nestjs/core (source) devDependencies minor 11.0.13 -> 11.1.0 age adoption passing confidence
@nestjs/platform-express (source) devDependencies minor 11.0.13 -> 11.1.0 age adoption passing confidence
@oxc-project/runtime (source) devDependencies minor ^0.63.0 -> ^0.65.0 age adoption passing confidence
@oxc-project/runtime (source) dependencies minor ^0.63.0 -> ^0.65.0 age adoption passing confidence
@swc/core (source) devDependencies patch 1.11.18 -> 1.11.21 age adoption passing confidence
@types/react (source) devDependencies patch 19.1.0 -> 19.1.2 age adoption passing confidence
@types/react-dom (source) devDependencies patch 19.1.1 -> 19.1.2 age adoption passing confidence
emnapi devDependencies patch 1.4.1 -> 1.4.3 age adoption passing confidence
esbuild devDependencies patch 0.25.2 -> 0.25.3 age adoption passing confidence
rolldown (source) devDependencies patch 1.0.0-beta.7 -> 1.0.0-beta.8 age adoption passing confidence
oxlint (source) devDependencies patch 0.16.6 -> 0.16.7 age adoption passing confidence
pnpm (source) packageManager minor 10.8.1 -> 10.9.0 age adoption passing confidence

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

Release Notes

napi-rs/napi-rs (@​napi-rs/cli)

v3.0.0-alpha.78

Compare Source

napi-rs/napi-rs (@​napi-rs/wasm-runtime)

v0.2.9

Compare Source

nestjs/nest (@​nestjs/core)

v11.1.0

Compare Source

v11.0.21

Compare Source

v11.0.20

Compare Source

v11.0.19

Compare Source

v11.0.18

Compare Source

What's Changed

Full Changelog: nestjs/nest@v11.0.17...v11.0.18

v11.0.17

Compare Source

v11.0.16

Compare Source

v11.0.15

Compare Source

v11.0.15 (2025-04-10)

Bug fixes
Committers: 1

v11.0.14

Compare Source

nestjs/nest (@​nestjs/platform-express)

v11.1.0

Compare Source

v11.0.21

Compare Source

v11.0.20

Compare Source

What's Changed

New Contributors

Full Changelog: nestjs/nest@v11.0.19...v11.0.20

v11.0.19

Compare Source

v11.0.18

Compare Source

What's Changed

Full Changelog: nestjs/nest@v11.0.17...v11.0.18

v11.0.17

Compare Source

v11.0.16

Compare Source

v11.0.15

Compare Source

v11.0.15 (2025-04-10)
Bug fixes
Committers: 1

v11.0.14

Compare Source

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

v1.11.21

Compare Source

Bug Fixes
Miscellaneous Tasks
Performance

v1.11.20

Compare Source

Bug Fixes

Related issue:

Features
Miscellaneous Tasks
Performance
Testing
toyobayashi/emnapi (emnapi)

v1.4.3

Compare Source

What's Changed

Full Changelog: toyobayashi/emnapi@v1.4.2...v1.4.3

v1.4.2

Compare Source

What's Changed

Full Changelog: toyobayashi/emnapi@v1.4.1...v1.4.2

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.

rolldown/rolldown (rolldown)

v1.0.0-beta.8

Compare Source

Bug Fixes
Features
Performance Improvements
oxc-project/oxc (oxlint)

v0.16.7: oxlint v0.16.7

Compare Source

[0.16.7] - 2025-04-21

Features
  • bb8a078 language_server: Use linter runtime / support import plugin (#​10268) (Sysix)
  • c94e6b8 linter: Allow eqeqeq to always be dangerously fixable (#​10499) (camchenry)
Bug Fixes
  • df488d4 language_server: Workspace edits as one batch when source.fixAll.oxc is the context (#​10428) (Sysix)
  • 2fc083c linter: Incorrect fix for prefer start ends with (#​10525) (camc314)
  • 020d8f8 linter: Fix auto-fix issue for eslint/no-else-return (#​10494) (yefan)
  • f0c1eff linter: False positve in no-unused-vars (#​10470) (camc314)
  • d690060 linter: Fix the auto-fix issue of the eslint/no-plusplus rule (#​10469) (yefan)
  • 72d5074 linter: False positive in eslint/no-redeclare (#​10402) (shulaoda)
  • c1f5623 linter: Add check for plugin_name when applying LintFilterKind::Rule (#​10339) (Ulrich Stark)
  • 4e1f536 linter: Config path resolution when path contains '..' syntax (#​10367) (Florian Bopp)
  • 58ab8ff parser: Adjust class start position when decorators are involved (#​10438) (Boshen)
Performance
  • 21f3175 langage_server: Prebuild IsolatedLintHandler (#​10406) (Sysix)
  • 62178c2 linter: Replace phf_set with array for DOM_PROPERTIES_NAMES (#​10501) (shulaoda)
  • 9280707 linter: Replace phf_set with array for DOM_ATTRIBUTES_TO_CAMEL (#​10500) (shulaoda)
  • 0a4f9d9 linter: Replace phf_set with array for ATTRIBUTE_TAGS_MAP (#​10498) (shulaoda)
  • 09f7358 linter: Replace phf_set with array in jsdoc/check-tag-names (#​10485) (shulaoda)
  • da87390 linter: Replace `phf_set

Configuration

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

@Brooooooklyn Brooooooklyn merged commit f8f7efc into main Apr 23, 2025
63 checks passed
@Brooooooklyn Brooooooklyn deleted the renovate/npm-packages branch April 23, 2025 15:41
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

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@Brooooooklyn