Skip to content

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

Merged
renovate[bot] merged 1 commit intomainfrom
renovate/npm-packages
Jul 20, 2025
Merged

chore(deps): lock file maintenance npm packages#211
renovate[bot] merged 1 commit intomainfrom
renovate/npm-packages

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Jul 20, 2025

This PR contains the following updates:

Package Type Update Change Age Adoption Passing Confidence
lockFileMaintenance All locks refreshed
@nestjs/common (source) devDependencies patch 11.1.3 -> 11.1.5 age adoption passing confidence
@nestjs/core (source) devDependencies patch 11.1.3 -> 11.1.5 age adoption passing confidence
@nestjs/platform-express (source) devDependencies patch 11.1.3 -> 11.1.5 age adoption passing confidence
@swc/core (source) devDependencies minor 1.12.11 -> 1.13.1 age adoption passing confidence
@types/node (source) devDependencies patch 24.0.13 -> 24.0.15 age adoption passing confidence
emnapi devDependencies patch 1.4.4 -> 1.4.5 age adoption passing confidence
oxlint (source) devDependencies minor 1.6.0 -> 1.7.0 age adoption passing confidence
rolldown (source) devDependencies patch 1.0.0-beta.27 -> 1.0.0-beta.28 age adoption passing confidence
esbuild devDependencies patch 0.25.6 -> 0.25.8 age adoption passing confidence

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

Release Notes

nestjs/nest (@​nestjs/common)

v11.1.5

Compare Source

v11.1.4

Compare Source

nestjs/nest (@​nestjs/core)

v11.1.5

Compare Source

v11.1.4

Compare Source

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

v11.1.5

Compare Source

v11.1.4

Compare Source

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

v1.13.1

Compare Source

Bug Fixes
Testing

v1.13.0

Compare Source

Bug Fixes
Features
Performance
Refactor

v1.12.14

Compare Source

Bug Fixes
Features

  • (es/parser) Enable support for dynamic import with defer phase (#​10845) (097d29d)

  • (plugin) Remove bytecheck to make Wasm plugins backward compatible (#​10842) (30ad808)

Miscellaneous Tasks
Performance
Refactor
Testing
toyobayashi/emnapi (emnapi)

v1.4.5

Compare Source

What's Changed

  • fix(wasm32-wasip1-threads): process never exit if trap in threads (#​156)

Full Changelog: toyobayashi/emnapi@v1.4.4...v1.4.5

oxc-project/oxc (oxlint)

v1.7.0

Compare Source

🚀 Features
  • a4dae73 linter: Introduce LintPlugins to store builtin + custom plugins (#​12117) (camc314)
rolldown/rolldown (rolldown)

v1.0.0-beta.28

Compare Source

🚀 Features
🐛 Bug Fixes
🚜 Refactor
📚 Documentation
⚡ Performance
🧪 Testing
  • rust: prevent meaningless snapshot change from bumping oxc runtime versions (#​5312) by @​hyf0
⚙️ Miscellaneous Tasks
❤️ New Contributors
evanw/esbuild (esbuild)

v0.25.8

Compare Source

  • Fix another TypeScript parsing edge case (#​4248)

    This fixes a regression with a change in the previous release that tries to more accurately parse TypeScript arrow functions inside the ?: operator. The regression specifically involves parsing an arrow function containing a #private identifier inside the middle of a ?: ternary operator inside a class body. This was fixed by propagating private identifier state into the parser clone used to speculatively parse the arrow function body. Here is an example of some affected code:

    class CachedDict {
  #has = (a: string) => dict.has(a);
  has = window
    ? (word: string): boolean => this.#has(word)
    : this.#has;
}

  • Fix a regression with the parsing of source phase imports

    The change in the previous release to parse source phase imports failed to properly handle the following cases:

    import source from 'bar'
import source from from 'bar'
import source type foo from 'bar'

    Parsing for these cases should now be fixed. The first case was incorrectly treated as a syntax error because esbuild was expecting the second case. And the last case was previously allowed but is now forbidden. TypeScript hasn't added this feature yet so it remains to be seen whether the last case will be allowed, but it's safer to disallow it for now. At least Babel doesn't allow the last case when parsing TypeScript, and Babel was involved with the source phase import specification.

v0.25.7

Compare Source

  • Parse and print JavaScript imports with an explicit phase (#​4238)

    This release adds basic syntax support for the defer and source import phases in JavaScript:

    • defer

      This is a stage 3 proposal for an upcoming JavaScript feature that will provide one way to eagerly load but lazily initialize imported modules. The imported module is automatically initialized on first use. Support for this syntax will also be part of the upcoming release of TypeScript 5.9. The syntax looks like this:

      import defer * as foo from "<specifier>";
const bar = await import.defer("<specifier>");

      Note that this feature deliberately cannot be used with the syntax import defer foo from "<specifier>" or import defer { foo } from "<specifier>".

    • source

      This is a stage 3 proposal for an upcoming JavaScript feature that will provide another way to eagerly load but lazily initialize imported modules. The imported module is returned in an uninitialized state. Support for this syntax may or may not be a part of TypeScript 5.9 (see this issue for details). The syntax looks like this:

      import source foo from "<specifier>";
const bar = await import.source("<specifier>");

      Note that this feature deliberately cannot be used with the syntax import defer * as foo from "<specifier>" or import defer { foo } from "<specifier>".

    This change only adds support for this syntax. These imports cannot currently be bundled by esbuild. To use these new features with esbuild's bundler, the imported paths must be external to the bundle and the output format must be set to esm.

  • Support optionally emitting absolute paths instead of relative paths (#​338, #​2082, #​3023)

    This release introduces the --abs-paths= feature which takes a comma-separated list of situations where esbuild should use absolute paths instead of relative paths. There are currently three supported situations: code (comments and string literals), log (log message text and location info), and metafile (the JSON build metadata).

    Using absolute paths instead of relative paths is not the default behavior because it means that the build results are no longer machine-independent (which means builds are no longer reproducible). Absolute paths can be useful when used with certain terminal emulators that allow you to click on absolute paths in the terminal text and/or when esbuild is being automatically invoked from several different directories within the same script.

  • Fix a TypeScript parsing edge case (#​4241)

    This release fixes an edge case with parsing an arrow function in TypeScript with a return type that's in the middle of a ?: ternary operator. For example:

    x = a ? (b) : c => d;
y = a ? (b) : c => d : e;

    The : token in the value assigned to x pairs with the ? token, so it's not the start of a return type annotation. However, the first : token in the value assigned to y is the start of a return type annotation because after parsing the arrow function body, it turns out there's another : token that can be used to pair with the ? token. This case is notable as it's the first TypeScript edge case that esbuild has needed a backtracking parser to parse. It has been addressed by a quick hack (cloning the whole parser) as it's a rare edge case and esbuild doesn't otherwise need a backtracking parser. Hopefully this is sufficient and doesn't cause any issues.

  • Inline small constant strings when minifying

    Previously esbuild's minifier didn't inline string constants because strings can be arbitrarily long, and this isn't necessarily a size win if the string is used more than once. Starting with this release, esbuild will now inline string constants when the length of the string is three code units or less. For example:

    // Original code
const foo = 'foo'
console.log({ [foo]: true })

// Old output (with --minify --bundle --format=esm)
var o="foo";console.log({[o]:!0});

// New output (with --minify --bundle --format=esm)
console.log({foo:!0});

    Note that esbuild's constant inlining only happens in very restrictive scenarios to avoid issues with TDZ handling. This change doesn't change when esbuild's constant inlining happens. It only expands the scope of it to include certain string literals in addition to numeric and boolean literals.

Configuration

📅 Schedule: Branch creation - "before 9am 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 enabled auto-merge (squash) July 20, 2025 20:44
@renovate renovate bot merged commit e007062 into main Jul 20, 2025
57 checks passed
@renovate renovate bot deleted the renovate/npm-packages branch July 20, 2025 20:50
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.

0 participants