fix(deps): update minor dependencies

[renovate]

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package	Change	Age	Confidence	Type	Update
@dotenvx/dotenvx	1.43.0 → 1.75.1			devDependencies	minor
@extractus/feed-extractor	7.1.7 → 7.2.1			dependencies	minor
@types/finalhandler (source)	1.2.3 → 1.2.4			devDependencies	patch
@types/node (source)	20.19.14 → 20.19.43			devDependencies	patch
@types/react (source)	18.3.24 → 18.3.31			devDependencies	patch
esbuild	^0.25.9 → ^0.28.0			devDependencies	minor
eslint-config-next (source)	15.0.2 → 15.5.20			devDependencies	minor
next (source)	15.5.3 → 15.5.20			dependencies	patch
node (source)	20.18.2 → 20.20.2				minor
npm-run-all2	6.2.3 → 6.2.6			devDependencies	patch
pnpm (source)	10.10.0 → 10.34.4			packageManager	minor
postcss (source)	8.5.6 → 8.5.16			devDependencies	patch
prettier (source)	3.5.3 → 3.9.4			devDependencies	minor
puppeteer (source)	23.3.1 → 23.11.1			pnpm.overrides	minor
puppeteer (source)	23.3.1 → 23.11.1			devDependencies	minor
react (source)	19.1.1 → 19.2.7			dependencies	minor
react-dom (source)	19.1.1 → 19.2.7			dependencies	minor
react-qr-code	2.0.18 → 2.2.0			dependencies	minor
serve-handler	6.1.5 → 6.1.7			dependencies	patch
tailwindcss (source)	3.4.17 → 3.4.19			devDependencies	patch
tsx (source)	4.20.5 → 4.23.0			devDependencies	minor
typescript (source)	5.9.2 → 5.9.3			devDependencies	patch
typescript (source)	5.6.2 → 5.9.3			devDependencies	minor
wireit	0.14.12 → 0.14.13			devDependencies	patch

---

Release Notes

dotenvx/dotenvx (@​dotenvx/dotenvx)

v1.75.1

Compare Source

Changed

• Publish as named binaries (#​851)

Removed

• Remove references to dotenvx-vlt (now dotenvx-armor) (#​849)

v1.75.0

Compare Source

Changed

• Swap in @dotenvx/primitives (#​848)
• ext commands become first-class(#​847)

v1.74.3

Compare Source

Changed

• Bundle dotenvx with @dotenvx/next-env for user convenience (#​845)

v1.74.2

Compare Source

Changed

• Fix provenance for @dotenvx/next-env (#​844)

v1.74.1

Compare Source

Added

• Add README for @dotenvx/next-env (#​843)

v1.73.1

Compare Source

Changed

• Give update available notification only for armor commands (#​840)

v1.73.0

Compare Source

Added

• Add dotenvx armor commands directly inside dotenvx (#​839)

dotenvx remains local-first: armor commands are optional under professional security section

v1.72.0

Compare Source

Added

• Move armor login command to first class dotenvx login command. (#​836)
• dotenvx remains local-first: login is optional and only needed when you want Armor features like moving keys off-device, team sharing, and audit access.
• Patch 2 high severity dependencies (#​837)

v1.71.3

Compare Source

Changed

• Forward command to Dotenvx Armor Key Guard approvals (#​835)

v1.71.2

Compare Source

Changed

• touch up get, set, and decrypt when armor installed (#​834)

v1.71.1

Compare Source

Changed

• stderr changed to inherit for dotenvx-armor integration (#​833)

v1.71.0

Compare Source

Added

• Add optional automation --token support for Armor ⛨ users (#​831)

v1.70.0

Compare Source

Changed

• Dotenvx Ops/Vlt is now Dotenvx Armor ⛨ (#​830)

v1.69.2

Compare Source

Changed

• Minor messaging improvements, especially if using armored keys (#​825)

v1.69.1

Compare Source

Changed

• Internally rename ops to vlt (#​823)

v1.69.0

Compare Source

Changed

• Remove fully-deprecated opsOff option in favor of noOps (#​822)

v1.68.1

Compare Source

Changed

• Pass -f to ops (#​821)

v1.68.0

Compare Source

Changed

• Support ignore option on parse (#​820)

v1.67.0

Compare Source

Added

• Add prompt for local storage vs armored storage (#​819)

v1.66.0

Compare Source

Added

• Add dotenvx doctor (#​815)

v1.65.3

Compare Source

Changed

• Improve spinner message blinking with simpler --no-spinner flag passed to ops (#​814)

v1.65.2

Compare Source

Changed

• Improve spinner message coordination between dotenvx and dotenvx-ops (#​813)

v1.65.1

Compare Source

Changed

• Prompts from ops should bubble up (#​812)

v1.65.0

Compare Source

Added

• Add support for replaceing duplicate keys with different values (#​806)

v1.64.0

Compare Source

Added

• Add optional dotenvx armor command.
  • armor up armor private key
  • armor down dearmor private key
  • armor push push armored key (from .env.keys)
  • armor pull pull armored key (into .env.keys)

Move private keys off device and under access control with Dotenvx Ops ⛨. Learn more

v1.63.0

Compare Source

Added

• Add support for encrypted values passed to --env flag (#​804)
• Add support for --format=colon in order to support cloudflare's wrangler --var flag format (#​804)

v1.62.0

Compare Source

Added

• Add support for config({ envs }). unlocks simpler cloudflare worker integration (#​803)

$ dotenvx encrypt -f .env.txt

// src/index.js
import envSrc from '../.env.txt'
import dotenvx from '@​dotenvx/dotenvx'

const config = dotenvx.config({ envs: [{ type: 'env', value: envSrc, privateKeyName: 'DOTENV_PRIVATE_KEY' }] })
const envx = config.parsed

export default {
  async fetch(request, env, ctx) {
    return new Response(`Hello ${envx.HELLO}`)
  }
}

"scripts": {
  "deploy": "wrangler deploy",
  "dev": "wrangler dev --var $(dotenvx keypair -f .env.txt --format=colon)",
  "start": "wrangler dev --var $(dotenvx keypair -f .env.txt --format=colon)",
  "test": "vitest"
},

v1.61.6

Compare Source

Changed

• Guard against command substitution following encrypted: (#​802)

v1.61.5

Compare Source

Changed

• Support --hostname flag to dotenvx-ops.login (#​801)

v1.61.4

Compare Source

Changed

• Respect SIGINT handler completion (#​798)

v1.61.3

Compare Source

Changed

• Tighten up ext precommit --install message (#​797)

v1.61.2

Compare Source

Changed

• For Ops ⛨ users surface stderr (#​796)

v1.61.1

Compare Source

Changed

• Faster coldstarts! (#​781)
• Patch dotenvx precommit|prebuild shorthand (#​793)

v1.61.0

Compare Source

Added

• Add login and logout method that proxy to dotenvx-ops login/logout (#​780)
• Note: dotenvx continues to make zero outgoing HTTP requests and includes no telemetry. Outgoing requests occur only if you explicitly install the dotenvx-ops SDK or CLI.

v1.60.2

Compare Source

Changed

• Communicate local key and armored key (for Ops stored keys) (#​778)

v1.60.1

Compare Source

Added

• Added missing + key ⛨ for Ops stored keys (#​777)

v1.60.0

Compare Source

Added

• Add spinner with loading messages
  • injecting (run)
  • encrypting (encrypt, set)
  • decrypting (decrypt, get)
  • rotating (rotate)
  • retrieving (keypair)

v1.59.1

Compare Source

Added

• add HELLO key to the kit sample to match most of our examples in the README

v1.59.0

Compare Source

Changed

• encrypt and set now create a .env file if one does not exist (#​771)
• pass --no-create to prevent file creation

v1.58.0

Compare Source

Changed

• Changed runtime injection message to format ⟐ injecting env (N) from FILE · dotenvx@VERSION (#​770)

v1.57.5

Compare Source

Changes

• Improve already installed message (#​768)

v1.57.4

Compare Source

Changes

• Use curl example for install dotenvx.com/ops (#​767)

v1.57.3

Compare Source

Changes

• Simplify installed success message (#​766)

v1.57.2

Compare Source

Changes

• Ran npm audit to update package-lock.json (#​763)

v1.57.1

Compare Source

Changes

• improved error logs and compacted most to a single line (#​755)

• introduced leading log glyphs as a visual status language:

  • ⟐ success action (injected)
  • ◈ success action (encrypted)
  • ◇ success action (set plain value, decrypted)
  • ⟳ success action (rotated)
  • ○ informational no-op (no changes)
  • ▣ success action for generated/updated support files
  • ⚠ warning
  • ☠ error

v1.57.0

Compare Source

Changed

• color and formatting changes to outputs (#​754)

v1.56.0

Compare Source

Changed

• ops off flag — now respected by get, keypair, rotate, and encrypt (#​750)
• --pp alias — added as shorthand for --pretty-print; toward sunsetting -pp (#​750)

Removed

• Remove support for .env.vault files (#​750)

v1.55.1

Compare Source

Added

• Respect dotenvx-ops status (on|off) (#​749)

v1.55.0

Compare Source

Added

• Add '⛨ ARMORED KEYS: Harden your private keys.' security feature when dotenvx-ops installed (#​746)

Removed

• Remove ProKeypair logic

v1.54.1

Compare Source

Changed

• Fix npm publish

v1.53.0

Compare Source

Removed

• Remove radar. It has been a year since replaced by ops. (#​743)

v1.52.0

Compare Source

Added

• Pass log level options to main.set (#​731)

v1.51.4

Compare Source

Changed

• Change description of dotenvx-ops to better reflect its tooling as operational primitives on top of dotenvx for production use cases. (#​721)

v1.51.3

Compare Source

Added

• Add hint on .env.keys for dotenvx armor up. Dotenvx Armor lets you armor your private keys securely with just a single command. It's a convenient alternative to manually copy/pasting them in and out of 1Password. (#​718)

v1.51.2

Compare Source

Changed

• Switch npm publish to use Dotenvx Ops' new Rotation Tokens (ROTs) (#​715)

This will allow us to start dogfooding our own solution for third-party API key rotation. Third-party API key rotation would drastically improve security industry wide. Please get in touch if this is interesting to you.

v1.51.1

Compare Source

Added

• Add opsOff type information

v1.51.0

Compare Source

Added

• Add config({opsOff: true}) options and --ops-off flag for turning off Dotenvx Ops features. (#​680)

v1.50.1

Compare Source

Removed

• Remove listed command to radar (now ops) (#​678)

v1.50.0

Compare Source

Added

• Add optional dotenvx ops command (#​677)
• Ops is a coming rename of Radar. Radar will become a feature inside ops.
• With dotenvx ops use dotenvx across your team, infrastructure, agents, and more.

 _______________________________________________________________________
|                                                                       |
|  dotenvx-ops: production grade dotenvx–with operational primitives    |
|                                                                       |
|  ░▒▓██████▓▒░░▒▓███████▓▒░ ░▒▓███████▓▒░                              |
| ░▒▓█▓▒░░▒▓█▓▒░▒▓█▓▒░░▒▓█▓▒░▒▓█▓▒░                                     |
| ░▒▓█▓▒░░▒▓█▓▒░▒▓█▓▒░░▒▓█▓▒░▒▓█▓▒░                                     |
| ░▒▓█▓▒░░▒▓█▓▒░▒▓███████▓▒░ ░▒▓██████▓▒░                               |
| ░▒▓█▓▒░░▒▓█▓▒░▒▓█▓▒░             ░▒▓█▓▒░                              |
| ░▒▓█▓▒░░▒▓█▓▒░▒▓█▓▒░             ░▒▓█▓▒░                              |
|  ░▒▓██████▓▒░░▒▓█▓▒░      ░▒▓███████▓▒░                               |
|                                                                       |
|  Learn more at https://dotenvx.com/ops                                |
|_______________________________________________________________________|

v1.49.1

Compare Source

Changed

• 🐞 patch bug with variable expansion of single quoted values (#​675)

v1.49.0

Compare Source

Added

• For precommit and prebuild, ignore .env.x file like we do with .env.vault file. (#​666)

v1.48.4

Compare Source

Removed

• Remove unnecessary use of eval in proKeypair helper (#​654)

v1.48.3

Compare Source

Changed

• Include privateKeyName and privateKey on internal processedEnv object (#​649)

v1.48.2

Compare Source

Changed

• Check radar status before sending (#​646)

v1.48.1

Compare Source

Changed

• Send beforEnv and afterEnv to Radar if user has installed (#​645)

v1.48.0

Compare Source

Added

• Include beforeEnv and afterEnv for user debugging (#​644)

v1.47.7

Compare Source

Changed

• src should be in internal processEnv object (#​643)

v1.47.6

Compare Source

Changed

• Make Radar call non-blocking (#​642)

v1.47.5

Compare Source

Changed

• Add resilient handling of any Radar failures (#​639)

v1.47.4

Compare Source

Changed

• Smarter require of non-installed libs like dotenvx-radar (#​638)

v1.47.3

Compare Source

Added

• Send to radar#observe if Radar installed by user (#​631)

Removed

• Remove cli in package.json (#​632)

v1.47.2

Compare Source

Added

• Export cli in package.json (#​629)

v1.47.1

Compare Source

Added

• Add convenience log that radar active 📡 when dotenvx-radar is installed (#​625)

v1.47.0

Compare Source

Added

• Add optional dotenvx radar command (#​624)
• Radar is an early access commercial extension for dotenvx that will auto backup your .env files.

 _______________________________________________________________________
|                                                                       |
|  Dotenvx Radar: Env Observability                                     |
|                                                                       |
|  ░▒▓███████▓▒░ ░▒▓██████▓▒░░▒▓███████▓▒░ ░▒▓██████▓▒░░▒▓███████▓▒░    |
|  ░▒▓█▓▒░░▒▓█▓▒░▒▓█▓▒░░▒▓█▓▒░▒▓█▓▒░░▒▓█▓▒░▒▓█▓▒░░▒▓█▓▒░▒▓█▓▒░░▒▓█▓▒░   |
|  ░▒▓█▓▒░░▒▓█▓▒░▒▓█▓▒░░▒▓█▓▒░▒▓█▓▒░░▒▓█▓▒░▒▓█▓▒░░▒▓█▓▒░▒▓█▓▒░░▒▓█▓▒░   |
|  ░▒▓███████▓▒░░▒▓████████▓▒░▒▓█▓▒░░▒▓█▓▒░▒▓████████▓▒░▒▓███████▓▒░    |
|  ░▒▓█▓▒░░▒▓█▓▒░▒▓█▓▒░░▒▓█▓▒░▒▓█▓▒░░▒▓█▓▒░▒▓█▓▒░░▒▓█▓▒░▒▓█▓▒░░▒▓█▓▒░   |
|  ░▒▓█▓▒░░▒▓█▓▒░▒▓█▓▒░░▒▓█▓▒░▒▓█▓▒░░▒▓█▓▒░▒▓█▓▒░░▒▓█▓▒░▒▓█▓▒░░▒▓█▓▒░   |
|  ░▒▓█▓▒░░▒▓█▓▒░▒▓█▓▒░░▒▓█▓▒░▒▓███████▓▒░░▒▓█▓▒░░▒▓█▓▒░▒▓█▓▒░░▒▓█▓▒░   |
|                                                                       |
|  Observe, version, and back up your environment variables at runtime. |
|                                                                       |
|  Purchase lifetime access at https://dotenvx.com/radar                |
|                                                                       |
| --------------------------------------------------------------------- |
| - thank you for using dotenvx! - @​motdotla                            |
|_______________________________________________________________________|

v1.46.0

Compare Source

Added

• Add error when hoisting issue experienced around commander.js (#​623)

Removed

• Remove git-dotenvx and git dotenvx shorthand (#​621)

v1.45.2

Compare Source

Changed

• Minor README updates

v1.45.1

Compare Source

Changed

• Include setLogName and setLogVersion in config (#​613)

v1.45.0

Compare Source

Added

• Add logger.setName and logger.setVersion for customization of logger (#​612)

v1.44.2

Compare Source

Changed

• Clarify license is BSD-3.

v1.44.1

Compare Source

Changed

• Patch SetOutput type (#​597)

v1.44.0

Compare Source

Added

• Add armv7 support (#​593)

extractus/feed-extractor (@​extractus/feed-extractor)

v7.2.1

Compare Source

• Replace outdated bellajs with @​pwshub/bellajs

v7.2.0

Compare Source

• Add AI Agents guides
• Fix some minor issues
• Fix old issues:
  • Relative links not resolved with baseUrl (#​135)
  • Atom / feed descriptions returned as objects (#​137)
• Update packakges
• Correct type definitions
• Update CI config

evanw/esbuild (esbuild)

v0.28.1

Compare Source

• Disallow \ in local development server HTTP requests (GHSA-g7r4-m6w7-qqqr)

  This release fixes a security issue where HTTP requests to esbuild's local development server could traverse outside of the serve directory on Windows using a \ backslash character. It happened due to the use of Go's path.Clean() function, which only handles Unix-style / characters. HTTP requests with paths containing \ are no longer allowed.

  Thanks to @​dellalibera for reporting this issue.

• Add integrity checks to the Deno API (GHSA-gv7w-rqvm-qjhr)

  The previous release of esbuild added integrity checks to esbuild's npm install script. This release also adds integrity checks to esbuild's Deno install script. Now esbuild's Deno API will also fail with an error if the downloaded esbuild binary contains something other than the expected content.

  Note that esbuild's Deno API installs from registry.npmjs.org by default, but allows the NPM_CONFIG_REGISTRY environment variable to override this with a custom package registry. This change means that the esbuild executable served by NPM_CONFIG_REGISTRY must now match the expected content.

  Thanks to @​sondt99 for reporting this issue.

• Avoid inlining using and await using declarations (#​4482)

  Previously esbuild's minifier sometimes incorrectly inlined using and await using declarations into subsequent uses of that declaration, which then fails to dispose of the resource correctly. This bug happened because inlining was done for let and const declarations by avoiding doing it for var declarations, which no longer worked when more declaration types were added. Here's an example:

  // Original code
  {
    using x = new Resource()
    x.activate()
  }
  
  // Old output (with --minify)
  new Resource().activate();
  
  // New output (with --minify)
  {using e=new Resource;e.activate()}

• Fix module evaluation when an error is thrown (#​4461, #​4467)

  If an error is thrown during module evaluation, esbuild previously didn't preserve the state of the module for subsequent module references. This was observable if import() or require() is used to import a module multiple times. The thrown error is supposed to be thrown by every call to import() or require(), not just the first. With this release, esbuild will now throw the same error every time you call import() or require() on a module that throws during its evaluation.

• Fix some edge cases around the new operator (#​4477)

  Previously esbuild incorrectly printed certain edge cases involving complex expressions inside the target of a new expression (specifically an optional chain and/or a tagged template literal). The generated code for the new target was not correctly wrapped with parentheses, and either contained a syntax error or had different semantics. These edge cases have been fixed so that they now correctly wrap the new target in parentheses. Here is an example of some affected code:

  // Original code
  new (foo()`bar`)()
  new (foo()?.bar)()
  
  // Old output
  new foo()`bar`();
  new (foo())?.bar();
  
  // New output
  new (foo())`bar`();
  new (foo()?.bar)();

• Fix renaming of nested var declarations (#​4471)

  This release fixes a bug where var declarations in nested scopes that are hoisted up to module scope were not correctly being renamed during bundling. That could previously lead to name collisions when minification was disabled, which could potentially cause a behavior change. The bug has been fixed so that these hoisted declarations are now considered to be module-level symbols during the name collision avoidance pass.

• Emit var instead of const for certain TypeScript-only constructs for ES5 (#​4448)

  While esbuild doesn't generally support converting const to var for ES5 due to nested scoping rules (which is currently a build-time error), esbuild previously incorrectly converted TypeScript-only import assignment constructs into a const declaration even when targeting ES5. With this release, esbuild will now use var for this case instead:

  // Original code
  import x = require('y')
  
  // Old output (with --target=es5)
  const x = require("y");
  
  // New output (with --target=es5)
  var x = require("y");

v0.28.0

Compare Source

• Add support for with { type: 'text' } imports (#​4435)

  The import text proposal has reached stage 3 in the TC39 process, which means that it's recommended for implementation. It has also already been implemented by Deno and Bun. So with this release, esbuild also adds support for it. This behaves exactly the same as esbuild's existing text loader. Here's an example:

  import string from './example.txt' with { type: 'text' }
  console.log(string)

• Add integrity checks to fallback download path (#​4343)

  Installing esbuild via npm is somewhat complicated with several different edge cases (see esbuild's documentation for details). If the regular installation of esbuild's platform-specific package fails, esbuild's install script attempts to download the platform-specific package itself (first with the npm command, and then with a HTTP request to registry.npmjs.org as a last resort).

  This last resort path previously didn't have any integrity checks. With this release, esbuild will now verify that the hash of the downloaded binary matches the expected hash for the current release. This means the hashes for all of esbuild's platform-specific binary packages will now be embedded in the top-level esbuild package. Hopefully this should work without any problems. But just in case, this change is being done as a breaking change release.

• Update the Go compiler from 1.25.7 to 1.26.1

  This upgrade should not affect anything. However, there have been some significant internal changes to the Go compiler, so esbuild could potentially behave differently in certain edge cases:

  • It now uses the new garbage collector that comes with Go 1.26.
  • The Go compiler is now more aggressive with allocating memory on the stack.
  • The executable format that the Go linker uses has undergone several changes.
  • The WebAssembly build now unconditionally makes use of the sign extension and non-trapping floating-point to integer conversion instructions.

  You can read the Go 1.26 release notes for more information.

v0.27.7

Compare Source

• Fix lowering of define semantics for TypeScript parameter properties (#​4421)

  The previous release incorrectly generated class fields for TypeScript parameter properties even when the configured target environment does not support class fields. With this release, the generated class fields will now be correctly lowered in this case:

  // Original code
  class Foo {
    constructor(public x = 1) {}
    y = 2
  }
  
  // Old output (with --loader=ts --target=es2021)
  class Foo {
    constructor(x = 1) {
      this.x = x;
      __publicField(this, "y", 2);
    }
    x;
  }
  
  // New output (with --loader=ts --target=es2021)
  class Foo {
    constructor(x = 1) {
      __publicField(this, "x", x);
      __publicField(this, "y", 2);
    }
  }

v0.27.5

Compare Source

• Fix for an async generator edge case (#​4401, #​4417)

  Support for transforming async generators into the equivalent state machine was added in version 0.19.0. However, the generated state machine didn't work correctly when polling async generators concurrently, such as in the following code:

  async function* inner() { yield 1; yield 2 }
  async function* outer() { yield* inner() }
  let gen = outer()
  for await (let x of [gen.next(), gen.next()]) console.log(x)

  Previously esbuild's output of the above code behaved incorrectly when async generators were transformed (such as with --supported:async-generator=false). The transformation should be fixed starting with this release.

  This fix was contributed by @​2767mr.

• Fix a regression when metafile is enabled (#​4420, #​4418)

  This release fixes a regression introduced by the previous release. When metafile: true was enabled in esbuild's JavaScript API, builds with build errors were incorrectly throwing an error about an empty JSON string instead of an object containing the build errors.

• Use define semantics for TypeScript parameter properties (#​4421)

  Parameter properties are a TypeScript-specific code generation feature that converts constructor parameters into class fields when they are prefixed by certain keywords. When "useDefineForClassFields": true is present in tsconfig.json, the TypeScript compiler automatically generates class field declarations for parameter properties. Previously esbuild didn't do this, but esbuild will now do this starting with this release:

  // Original code
  class Foo {
    constructor(public x: number) {}
  }
  
  // Old output (with --loader=ts)
  class Foo {
    constructor(x) {
      this.x = x;
    }
  }
  
  // New output (with --loader=ts)
  class Foo {
    constructor(x) {
      this.x = x;
    }
    x;
  }

• Allow es2025 as a target in tsconfig.json (#​4432)

  TypeScript recently added es2025 as a compilation target, so esbuild now supports this in the target field of tsconfig.json files, such as in the following configuration file:

  {
    "compilerOptions": {
      "target": "ES2025"
    }
  }

  As a reminder, the only thing that esbuild uses this field for is determining whether or not to use legacy TypeScript behavior for class fields. You can read more in the documentation.

v0.27.4

Compare Source

• Fix a regression with CSS media queries (#​4395, #​4405, #​4406)

  Version 0.25.11 of esbuild introduced support for parsing media queries. This unintentionally introduced a regression with printing media queries that use the <media-type> and <media-condition-without-or> grammar. Specifically, esbuild was failing to wrap an or clause with parentheses when inside <media-condition-without-or>. This release fixes the regression.

  Here is an example:

  /* Original code */
  @​media only screen and ((min-width: 10px) or (min-height: 10px)) {
    a { color: red }
  }
  
  /* Old output (incorrect) */
  @​media only screen and (min-width: 10px) or (min-height: 10px) {
    a {
      color: red;
    }
  }
  
  /* New output (correct) *

✂ Note

PR body was truncated to here.

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• 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.