fix(deps): update all non-major dependencies

[renovate-bot]

This PR contains the following updates:

Package	Change	Age	Confidence
@lerna-lite/cli (source)	^4.10.2 → ^4.10.5
@lerna-lite/publish (source)	^4.10.2 → ^4.10.5
@lerna-lite/watch (source)	^4.10.2 → ^4.10.5
@types/node (source)	^24.10.1 → ^24.10.4
autoprefixer	^10.4.22 → ^10.4.23
dompurify	^3.3.0 → ^3.3.1
esbuild	^0.27.0 → ^0.27.2
remove-glob	^0.4.4 → ^0.4.10
sass	^1.93.3 → ^1.97.2
vite (source)	^7.2.2 → ^7.3.1

---

Release Notes

lerna-lite/lerna-lite (@​lerna-lite/cli)

v4.10.5

Compare Source

Note: Version bump only for package @​lerna-lite/cli

v4.10.4

Compare Source

Note: Version bump only for package @​lerna-lite/cli

v4.10.3

Compare Source

Note: Version bump only for package @​lerna-lite/cli

lerna-lite/lerna-lite (@​lerna-lite/publish)

v4.10.5

Compare Source

Note: Version bump only for package @​lerna-lite/publish

v4.10.4

Compare Source

Note: Version bump only for package @​lerna-lite/publish

v4.10.3

Compare Source

🐞 Bug Fixes

• Version/Publish --yes log should show only after all Changes logged (#​1214) (cd1e474) - by @​ghiscoding

lerna-lite/lerna-lite (@​lerna-lite/watch)

v4.10.5

Compare Source

Note: Version bump only for package @​lerna-lite/watch

v4.10.4

Compare Source

Note: Version bump only for package @​lerna-lite/watch

v4.10.3

Compare Source

Note: Version bump only for package @​lerna-lite/watch

postcss/autoprefixer (autoprefixer)

v10.4.23

Compare Source

• Reduced dependencies (by @​hyperz111).

cure53/DOMPurify (dompurify)

v3.3.1: DOMPurify 3.3.1

Compare Source

• Updated ADD_FORBID_CONTENTS setting to extend default list, thanks @​MariusRumpf
• Updated the ESM import syntax to be more correct, thanks @​binhpv

evanw/esbuild (esbuild)

v0.27.2

Compare Source

• Allow import path specifiers starting with #/ (#​4361)

  Previously the specification for package.json disallowed import path specifiers starting with #/, but this restriction has recently been relaxed and support for it is being added across the JavaScript ecosystem. One use case is using it for a wildcard pattern such as mapping #/* to ./src/* (previously you had to use another character such as #_* instead, which was more confusing). There is some more context in nodejs/node#49182.

  This change was contributed by @​hybrist.

• Automatically add the -webkit-mask prefix (#​4357, #​4358)

  This release automatically adds the -webkit- vendor prefix for the mask CSS shorthand property:

  /* Original code */
  main {
    mask: url(x.png) center/5rem no-repeat
  }
  
  /* Old output (with --target=chrome110) */
  main {
    mask: url(x.png) center/5rem no-repeat;
  }
  
  /* New output (with --target=chrome110) */
  main {
    -webkit-mask: url(x.png) center/5rem no-repeat;
    mask: url(x.png) center/5rem no-repeat;
  }

  This change was contributed by @​BPJEnnova.

• Additional minification of switch statements (#​4176, #​4359)

  This release contains additional minification patterns for reducing switch statements. Here is an example:

  // Original code
  switch (x) {
    case 0:
      foo()
      break
    case 1:
    default:
      bar()
  }
  
  // Old output (with --minify)
  switch(x){case 0:foo();break;case 1:default:bar()}
  
  // New output (with --minify)
  x===0?foo():bar();

• Forbid using declarations inside switch clauses (#​4323)

  This is a rare change to remove something that was previously possible. The Explicit Resource Management proposal introduced using declarations. These were previously allowed inside case and default clauses in switch statements. This had well-defined semantics and was already widely implemented (by V8, SpiderMonkey, TypeScript, esbuild, and others). However, it was considered to be too confusing because of how scope works in switch statements, so it has been removed from the specification. This edge case will now be a syntax error. See tc39/proposal-explicit-resource-management#215 and rbuckton/ecma262#14 for details.

  Here is an example of code that is no longer allowed:

  switch (mode) {
    case 'read':
      using readLock = db.read()
      return readAll(readLock)
  
    case 'write':
      using writeLock = db.write()
      return writeAll(writeLock)
  }

  That code will now have to be modified to look like this instead (note the additional { and } block statements around each case body):

  switch (mode) {
    case 'read': {
      using readLock = db.read()
      return readAll(readLock)
    }
    case 'write': {
      using writeLock = db.write()
      return writeAll(writeLock)
    }
  }

  This is not being released in one of esbuild's breaking change releases since this feature hasn't been finalized yet, and esbuild always tracks the current state of the specification (so esbuild's previous behavior was arguably incorrect).

v0.27.1

Compare Source

• Fix bundler bug with var nested inside if (#​4348)

  This release fixes a bug with the bundler that happens when importing an ES module using require (which causes it to be wrapped) and there's a top-level var inside an if statement without being wrapped in a { ... } block (and a few other conditions). The bundling transform needed to hoist these var declarations outside of the lazy ES module wrapper for correctness. See the issue for details.

• Fix minifier bug with for inside try inside label (#​4351)

  This fixes an old regression from version v0.21.4. Some code was introduced to move the label inside the try statement to address a problem with transforming labeled for await loops to avoid the await (the transformation involves converting the for await loop into a for loop and wrapping it in a try statement). However, it introduces problems for cross-compiled JVM code that uses all three of these features heavily. This release restricts this transform to only apply to for loops that esbuild itself generates internally as part of the for await transform. Here is an example of some affected code:

  // Original code
  d: {
    e: {
      try {
        while (1) { break d }
      } catch { break e; }
    }
  }
  
  // Old output (with --minify)
  a:try{e:for(;;)break a}catch{break e}
  
  // New output (with --minify)
  a:e:try{for(;;)break a}catch{break e}

• Inline IIFEs containing a single expression (#​4354)

  Previously inlining of IIFEs (immediately-invoked function expressions) only worked if the body contained a single return statement. Now it should also work if the body contains a single expression statement instead:

  // Original code
  const foo = () => {
    const cb = () => {
      console.log(x())
    }
    return cb()
  }
  
  // Old output (with --minify)
  const foo=()=>(()=>{console.log(x())})();
  
  // New output (with --minify)
  const foo=()=>{console.log(x())};

• The minifier now strips empty finally clauses (#​4353)

  This improvement means that finally clauses containing dead code can potentially cause the associated try statement to be removed from the output entirely in minified builds:

  // Original code
  function foo(callback) {
    if (DEBUG) stack.push(callback.name);
    try {
      callback();
    } finally {
      if (DEBUG) stack.pop();
    }
  }
  
  // Old output (with --minify --define:DEBUG=false)
  function foo(a){try{a()}finally{}}
  
  // New output (with --minify --define:DEBUG=false)
  function foo(a){a()}

• Allow tree-shaking of the Symbol constructor

  With this release, calling Symbol is now considered to be side-effect free when the argument is known to be a primitive value. This means esbuild can now tree-shake module-level symbol variables:

  // Original code
  const a = Symbol('foo')
  const b = Symbol(bar)
  
  // Old output (with --tree-shaking=true)
  const a = Symbol("foo");
  const b = Symbol(bar);
  
  // New output (with --tree-shaking=true)
  const b = Symbol(bar);

ghiscoding/remove-glob (remove-glob)

v0.4.10

Compare Source

Bug Fixes

• reapply force .js extension in imports (dda6bc9)

v0.4.9

Compare Source

v0.4.8

Compare Source

v0.4.7

Compare Source

v0.4.6

Compare Source

Bug Fixes

• deps: update all non-major dependencies (7c841e1)
• use -V for verbose flag to avoid duplicate flag usage (3ac70c3)

v0.4.5

Compare Source

sass/dart-sass (sass)

v1.97.2

Compare Source

• Additional fixes for implicit configuration when nested imports are involved.

v1.97.1

Compare Source

v1.97.0

Compare Source

• Add support for the display-p3-linear color space.

v1.96.0

Compare Source

• Allow numbers with complex units (more than one numerator unit or more than
  zero denominator units) to be emitted to CSS. These are now emitted as
  calc() expressions, which now support complex units in plain CSS.

v1.95.1

Compare Source

• No user-visible changes.

v1.95.0

Compare Source

• Add support for the CSS-style if() function. In addition to supporting the
  plain CSS syntax, this also supports a sass() query that takes a Sass
  expression that evaluates to true or false at preprocessing time depending
  on whether the Sass value is truthy. If there are no plain-CSS queries, the
  function will return the first value whose query returns true during
  preprocessing. For example, if(sass(false): 1; sass(true): 2; else: 3)
  returns 2.

• The old Sass if() syntax is now deprecated. Users are encouraged to migrate
  to the new CSS syntax. if($condition, $if-true, $if-false) can be changed to
  if(sass($condition): $if-true; else: $if-false).

  See the Sass website for details.

• Plain-CSS if() functions are now considered "special numbers", meaning that
  they can be used in place of arguments to CSS color functions.

• Plain-CSS if() functions and attr() functions are now considered "special
  variable strings" (like var()), meaning they can now be used in place of
  multiple arguments or syntax fragments in various CSS functions.

v1.94.3

Compare Source

• Fix the span reported for standalone % expressions followed by whitespace.

v1.94.2

Compare Source

Command-Line Interface

• Using --fatal-deprecation <version> no longer emits warnings about
  deprecations that are obsolete.

Dart API

• Deprecation.forVersion now excludes obsolete deprecations from the set it
  returns.

JS API

• Excludes obsolete deprecations from fatalDeprecations when a Version is
  passed.

Node.js Embedded Host

• Fix a bug where a variable could be used before it was initialized during
  async compilation.

v1.94.1

Compare Source

• No user-visible changes.

v1.94.0

Compare Source

• Potentially breaking compatibility fix: @function rules whose names
  begin with -- are now parsed as unknown at-rules to support the plain CSS
  @function rule. Within this rule, the result property is parsed as raw
  CSS just like custom properties.

• Potentially breaking compatibility fix: @mixin rules whose names begin
  with -- are now errors. These are not yet parsed as unknown at-rules because
  no browser currently supports CSS mixins.

vitejs/vite (vite)

v7.3.1

Compare Source

Please refer to CHANGELOG.md for details.

v7.3.0

Compare Source

Please refer to CHANGELOG.md for details.

v7.2.7

Compare Source

v7.2.6

Compare Source

7.2.6 (2025-12-01)

v7.2.4

Compare Source

Bug Fixes

• revert "perf(deps): replace debug with obug (#​21107)" (2d66b7b)

v7.2.3

Compare Source

Bug Fixes

• allow multiple bindCLIShortcuts calls with shortcut merging (#​21103) (5909efd)
• deps: update all non-major dependencies (#​21096) (6a34ac3)
• deps: update all non-major dependencies (#​21128) (4f8171e)

Performance Improvements

• deps: replace debug with obug (#​21107) (acfe939)

Miscellaneous Chores

• deps: update dependency @​rollup/plugin-commonjs to v29 (#​21099) (02ceaec)
• deps: update rolldown-related dependencies (#​21095) (39a0a15)
• deps: update rolldown-related dependencies (#​21127) (5029720)

---

Configuration

📅 Schedule: Branch creation - "every 3 months" (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 was generated by Mend Renovate. View the repository job log.

[github-actions]

Playwright E2E Test Results

83 tests  ±0   83 ✅ ±0   1m 43s ⏱️ -1s
73 suites ±0    0 💤 ±0 
 1 files   ±0    0 ❌ ±0 

Results for commit e63f8a2. ± Comparison against base commit 5421638.

♻️ This comment has been updated with latest results.

[github-actions]

🎉 This pull request is included in version 5.0.0 📦
🔗 The release notes are available at: GitHub Release 🚀