Update all dependencies - autoclosed #2

renovate · 2024-05-26T10:52:27Z

This PR contains the following updates:

Package	Change	Type	Update
@inquirer/core (source)	`8.1.0` -> `8.2.2`	devDependencies	minor
@inquirer/prompts (source)	`5.0.2` -> `5.0.5`	devDependencies	patch
esbuild	`0.20.2` -> `0.21.4`	devDependencies	minor
markdown-link-check	`3.12.1` -> `3.12.2`	devDependencies	patch
renovatebot/github-action	`v40.1.11` -> `v40.1.12`	action	patch
svgo (source)	`3.2.0` -> `3.3.2`	devDependencies	minor

Release Notes

SBoudrias/Inquirer.js (@inquirer/core)

`v8.2.2`

Compare Source

Fix bugs with the rawlist

`v8.2.1`

Compare Source

Fix bug when using both arrow keys and number keys on the rawList prompt.
Dependencies bump

`v8.2.0`

Compare Source

checkbox prompt: Update the help message to be more complete. And the help message is now shown until a selection is made.

evanw/esbuild (esbuild)

`v0.21.4`

Compare Source

Update support for import assertions and import attributes in node (#3778)

Import assertions (the assert keyword) have been removed from node starting in v22.0.0. So esbuild will now strip them and generate a warning with --target=node22 or above:
```
▲ [WARNING] The "assert" keyword is not supported in the configured target environment ("node22") [assert-to-with]

    example.mjs:1:40:
      1 │ import json from "esbuild/package.json" assert { type: "json" }
        │                                         ~~~~~~
        ╵                                         with

  Did you mean to use "with" instead of "assert"?
```
Import attributes (the with keyword) have been backported to node 18 starting in v18.20.0. So esbuild will no longer strip them with --target=node18.N if N is 20 or greater.

Fix for await transform when a label is present

This release fixes a bug where the for await transform, which wraps the loop in a try statement, previously failed to also move the loop's label into the try statement. This bug only affects code that uses both of these features in combination. Here's an example of some affected code:

// Original code
async function test() {
  outer: for await (const x of [Promise.resolve([0, 1])]) {
    for (const y of x) if (y) break outer
    throw 'fail'
  }
}

// Old output (with --target=es6)
function test() {
  return __async(this, null, function* () {
    outer: try {
      for (var iter = __forAwait([Promise.resolve([0, 1])]), more, temp, error; more = !(temp = yield iter.next()).done; more = false) {
        const x = temp.value;
        for (const y of x) if (y) break outer;
        throw "fail";
      }
    } catch (temp) {
      error = [temp];
    } finally {
      try {
        more && (temp = iter.return) && (yield temp.call(iter));
      } finally {
        if (error)
          throw error[0];
      }
    }
  });
}

// New output (with --target=es6)
function test() {
  return __async(this, null, function* () {
    try {
      outer: for (var iter = __forAwait([Promise.resolve([0, 1])]), more, temp, error; more = !(temp = yield iter.next()).done; more = false) {
        const x = temp.value;
        for (const y of x) if (y) break outer;
        throw "fail";
      }
    } catch (temp) {
      error = [temp];
    } finally {
      try {
        more && (temp = iter.return) && (yield temp.call(iter));
      } finally {
        if (error)
          throw error[0];
      }
    }
  });
}

Do additional constant folding after cross-module enum inlining (#3416, #3425)

This release adds a few more cases where esbuild does constant folding after cross-module enum inlining.

// Original code: enum.ts
export enum Platform {
  WINDOWS = 'windows',
  MACOS = 'macos',
  LINUX = 'linux',
}

// Original code: main.ts
import { Platform } from './enum';
declare const PLATFORM: string;
export function logPlatform() {
  if (PLATFORM == Platform.WINDOWS) console.log('Windows');
  else if (PLATFORM == Platform.MACOS) console.log('macOS');
  else if (PLATFORM == Platform.LINUX) console.log('Linux');
  else console.log('Other');
}

// Old output (with --bundle '--define:PLATFORM="macos"' --minify --format=esm)
function n(){"windows"=="macos"?console.log("Windows"):"macos"=="macos"?console.log("macOS"):"linux"=="macos"?console.log("Linux"):console.log("Other")}export{n as logPlatform};

// New output (with --bundle '--define:PLATFORM="macos"' --minify --format=esm)
function n(){console.log("macOS")}export{n as logPlatform};

Pass import attributes to on-resolve plugins (#3384, #3639, #3646)

With this release, on-resolve plugins will now have access to the import attributes on the import via the with property of the arguments object. This mirrors the with property of the arguments object that's already passed to on-load plugins. In addition, you can now pass with to the resolve() API call which will then forward that value on to all relevant plugins. Here's an example of a plugin that can now be written:

const examplePlugin = {
  name: 'Example plugin',
  setup(build) {
    build.onResolve({ filter: /.*/ }, args => {
      if (args.with.type === 'external')
        return { external: true }
    })
  }
}

require('esbuild').build({
  stdin: {
    contents: `
      import foo from "./foo" with { type: "external" }
      foo()
    `,
  },
  bundle: true,
  format: 'esm',
  write: false,
  plugins: [examplePlugin],
}).then(result => {
  console.log(result.outputFiles[0].text)
})

Formatting support for the @position-try rule (#3773)

Chrome shipped this new CSS at-rule in version 125 as part of the CSS anchor positioning API. With this release, esbuild now knows to expect a declaration list inside of the @position-try body block and will format it appropriately.
Always allow internal string import and export aliases (#3343)

Import and export names can be string literals in ES2022+. Previously esbuild forbid any usage of these aliases when the target was below ES2022. Starting with this release, esbuild will only forbid such usage when the alias would otherwise end up in output as a string literal. String literal aliases that are only used internally in the bundle and are "compiled away" are no longer errors. This makes it possible to use string literal aliases with esbuild's inject feature even when the target is earlier than ES2022.

`v0.21.3`

Compare Source

Implement the decorator metadata proposal (#3760)

This release implements the decorator metadata proposal, which is a sub-proposal of the decorators proposal. Microsoft shipped the decorators proposal in TypeScript 5.0 and the decorator metadata proposal in TypeScript 5.2, so it's important that esbuild also supports both of these features. Here's a quick example:
```
// Shim the "Symbol.metadata" symbol
Symbol.metadata ??= Symbol('Symbol.metadata')

const track = (_, context) => {
  (context.metadata.names ||= []).push(context.name)
}

class Foo {
  @&#8203;track foo = 1
  @&#8203;track bar = 2
}

// Prints ["foo", "bar"]
console.log(Foo[Symbol.metadata].names)
```
⚠️ WARNING ⚠️

This proposal has been marked as "stage 3" which means "recommended for implementation". However, it's still a work in progress and isn't a part of JavaScript yet, so keep in mind that any code that uses JavaScript decorator metadata may need to be updated as the feature continues to evolve. If/when that happens, I will update esbuild's implementation to match the specification. I will not be supporting old versions of the specification.
Fix bundled decorators in derived classes (#3768)

In certain cases, bundling code that uses decorators in a derived class with a class body that references its own class name could previously generate code that crashes at run-time due to an incorrect variable name. This problem has been fixed. Here is an example of code that was compiled incorrectly before this fix:
```
class Foo extends Object {
  @&#8203;(x => x) foo() {
    return Foo
  }
}
console.log(new Foo().foo())
```
Fix tsconfig.json files inside symlinked directories (#3767)

This release fixes an issue with a scenario involving a tsconfig.json file that extends another file from within a symlinked directory that uses the paths feature. In that case, the implicit baseURL value should be based on the real path (i.e. after expanding all symbolic links) instead of the original path. This was already done for other files that esbuild resolves but was not yet done for tsconfig.json because it's special-cased (the regular path resolver can't be used because the information inside tsconfig.json is involved in path resolution). Note that this fix no longer applies if the --preserve-symlinks setting is enabled.

`v0.21.2`

Compare Source

Correct this in field and accessor decorators (#3761)

This release changes the value of this in initializers for class field and accessor decorators from the module-level this value to the appropriate this value for the decorated element (either the class or the instance). It was previously incorrect due to lack of test coverage. Here's an example of a decorator that doesn't work without this change:
```
const dec = () => function() { this.bar = true }
class Foo { @&#8203;dec static foo }
console.log(Foo.bar) // Should be "true"
```
Allow es2023 as a target environment (#3762)

TypeScript recently added es2023 as a compilation target, so esbuild now supports this too. There is no difference between a target of es2022 and es2023 as far as esbuild is concerned since the 2023 edition of JavaScript doesn't introduce any new syntax features.

`v0.21.1`

Compare Source

Fix a regression with --keep-names (#3756)

The previous release introduced a regression with the --keep-names setting and object literals with get/set accessor methods, in which case the generated code contained syntax errors. This release fixes the regression:
```
// Original code
x = { get y() {} }

// Output from version 0.21.0 (with --keep-names)
x = { get y: /* @&#8203;__PURE__ */ __name(function() {
}, "y") };

// Output from this version (with --keep-names)
x = { get y() {
} };
```

`v0.21.0`

Compare Source

This release doesn't contain any deliberately-breaking changes. However, it contains a very complex new feature and while all of esbuild's tests pass, I would not be surprised if an important edge case turns out to be broken. So I'm releasing this as a breaking change release to avoid causing any trouble. As usual, make sure to test your code when you upgrade.

Implement the JavaScript decorators proposal (#104)

With this release, esbuild now contains an implementation of the upcoming JavaScript decorators proposal. This is the same feature that shipped in TypeScript 5.0 and has been highly-requested on esbuild's issue tracker. You can read more about them in that blog post and in this other (now slightly outdated) extensive blog post here: https://2ality.com/2022/10/javascript-decorators.html. Here's a quick example:
```
const log = (fn, context) => function() {
  console.log(`before ${context.name}`)
  const it = fn.apply(this, arguments)
  console.log(`after ${context.name}`)
  return it
}

class Foo {
  @&#8203;log static foo() {
    console.log('in foo')
  }
}

// Logs "before foo", "in foo", "after foo"
Foo.foo()
```
Note that this feature is different than the existing "TypeScript experimental decorators" feature that esbuild already implements. It uses similar syntax but behaves very differently, and the two are not compatible (although it's sometimes possible to write decorators that work with both). TypeScript experimental decorators will still be supported by esbuild going forward as they have been around for a long time, are very widely used, and let you do certain things that are not possible with JavaScript decorators (such as decorating function parameters). By default esbuild will parse and transform JavaScript decorators, but you can tell esbuild to parse and transform TypeScript experimental decorators instead by setting "experimentalDecorators": true in your tsconfig.json file.

Probably at least half of the work for this feature went into creating a test suite that exercises many of the proposal's edge cases: https://github.com/evanw/decorator-tests. It has given me a reasonable level of confidence that esbuild's initial implementation is acceptable. However, I don't have access to a significant sample of real code that uses JavaScript decorators. If you're currently using JavaScript decorators in a real code base, please try out esbuild's implementation and let me know if anything seems off.

⚠️ WARNING ⚠️

This proposal has been in the works for a very long time (work began around 10 years ago in 2014) and it is finally getting close to becoming part of the JavaScript language. However, it's still a work in progress and isn't a part of JavaScript yet, so keep in mind that any code that uses JavaScript decorators may need to be updated as the feature continues to evolve. The decorators proposal is pretty close to its final form but it can and likely will undergo some small behavioral adjustments before it ends up becoming a part of the standard. If/when that happens, I will update esbuild's implementation to match the specification. I will not be supporting old versions of the specification.

Optimize the generated code for private methods

Previously when lowering private methods for old browsers, esbuild would generate one WeakSet for each private method. This mirrors similar logic for generating one WeakSet for each private field. Using a separate WeakMap for private fields is necessary as their assignment can be observable:

let it
class Bar {
  constructor() {
    it = this
  }
}
class Foo extends Bar {
  #x = 1
  #y = null.foo
  static check() {
    console.log(#x in it, #y in it)
  }
}
try { new Foo } catch {}
Foo.check()

This prints true false because this partially-initialized instance has #x but not #y. In other words, it's not true that all class instances will always have all of their private fields. However, the assignment of private methods to a class instance is not observable. In other words, it's true that all class instances will always have all of their private methods. This means esbuild can lower private methods into code where all methods share a single WeakSet, which is smaller, faster, and uses less memory. Other JavaScript processing tools such as the TypeScript compiler already make this optimization. Here's what this change looks like:

// Original code
class Foo {
  #x() { return this.#x() }
  #y() { return this.#y() }
  #z() { return this.#z() }
}

// Old output (--supported:class-private-method=false)
var _x, x_fn, _y, y_fn, _z, z_fn;
class Foo {
  constructor() {
    __privateAdd(this, _x);
    __privateAdd(this, _y);
    __privateAdd(this, _z);
  }
}
_x = new WeakSet();
x_fn = function() {
  return __privateMethod(this, _x, x_fn).call(this);
};
_y = new WeakSet();
y_fn = function() {
  return __privateMethod(this, _y, y_fn).call(this);
};
_z = new WeakSet();
z_fn = function() {
  return __privateMethod(this, _z, z_fn).call(this);
};

// New output (--supported:class-private-method=false)
var _Foo_instances, x_fn, y_fn, z_fn;
class Foo {
  constructor() {
    __privateAdd(this, _Foo_instances);
  }
}
_Foo_instances = new WeakSet();
x_fn = function() {
  return __privateMethod(this, _Foo_instances, x_fn).call(this);
};
y_fn = function() {
  return __privateMethod(this, _Foo_instances, y_fn).call(this);
};
z_fn = function() {
  return __privateMethod(this, _Foo_instances, z_fn).call(this);
};

Fix an obscure bug with lowering class members with computed property keys

When class members that use newer syntax features are transformed for older target environments, they sometimes need to be relocated. However, care must be taken to not reorder any side effects caused by computed property keys. For example, the following code must evaluate a() then b() then c():
```
class Foo {
  [a()]() {}
  [b()];
  static { c() }
}
```
Previously esbuild did this by shifting the computed property key forward to the next spot in the evaluation order. Classes evaluate all computed keys first and then all static class elements, so if the last computed key needs to be shifted, esbuild previously inserted a static block at start of the class body, ensuring it came before all other static class elements:
```
var _a;
class Foo {
  constructor() {
    __publicField(this, _a);
  }
  static {
    _a = b();
  }
  [a()]() {
  }
  static {
    c();
  }
}
```
However, this could cause esbuild to accidentally generate a syntax error if the computed property key contains code that isn't allowed in a static block, such as an await expression. With this release, esbuild fixes this problem by shifting the computed property key backward to the previous spot in the evaluation order instead, which may push it into the extends clause or even before the class itself:
```
// Original code
class Foo {
  [a()]() {}
  [await b()];
  static { c() }
}

// Old output (with --supported:class-field=false)
var _a;
class Foo {
  constructor() {
    __publicField(this, _a);
  }
  static {
    _a = await b();
  }
  [a()]() {
  }
  static {
    c();
  }
}

// New output (with --supported:class-field=false)
var _a, _b;
class Foo {
  constructor() {
    __publicField(this, _a);
  }
  [(_b = a(), _a = await b(), _b)]() {
  }
  static {
    c();
  }
}
```
Fix some --keep-names edge cases

The NamedEvaluation syntax-directed operation in the JavaScript specification gives certain anonymous expressions a name property depending on where they are in the syntax tree. For example, the following initializers convey a name value:
```
var foo = function() {}
var bar = class {}
console.log(foo.name, bar.name)
```
When you enable esbuild's --keep-names setting, esbuild generates additional code to represent this NamedEvaluation operation so that the value of the name property persists even when the identifiers are renamed (e.g. due to minification).

However, I recently learned that esbuild's implementation of NamedEvaluation is missing a few cases. Specifically esbuild was missing property definitions, class initializers, logical-assignment operators. These cases should now all be handled:
```
var obj = { foo: function() {} }
class Foo0 { foo = function() {} }
class Foo1 { static foo = function() {} }
class Foo2 { accessor foo = function() {} }
class Foo3 { static accessor foo = function() {} }
foo ||= function() {}
foo &&= function() {}
foo ??= function() {}
```

tcort/markdown-link-check (markdown-link-check)

renovatebot/github-action (renovatebot/github-action)

`v40.1.12`

Compare Source

Documentation

add section about commit signing using GitHub App (#838) (6537be5)
clarify file naming (#835) (e063ae9)
update references to actions/checkout to v4.1.5 (9f55642)
update references to actions/checkout to v4.1.6 (ef89c4f)
update references to ghcr.io/renovatebot/renovate to v37.342.1 (9912bcb)
update references to ghcr.io/renovatebot/renovate to v37.356.1 (fb25c83)
update references to ghcr.io/renovatebot/renovate to v37.385.0 (af35cfd)
update references to renovatebot/github-action to v40.1.11 (ded0be5)

Miscellaneous Chores

deps: update dependency @types/node to v20.12.10 (b03198a)
deps: update dependency @types/node to v20.12.11 (264a396)
deps: update dependency @types/node to v20.12.12 (38a7ea3)
deps: update dependency @types/node to v20.12.8 (809e5eb)
deps: update dependency @types/node to v20.12.9 (bfe08a7)
deps: update dependency lint-staged to v15.2.4 (e2c0ea7)
deps: update dependency lint-staged to v15.2.5 (d9d9189)
deps: update dependency npm-run-all2 to v6.2.0 (05e22d8)
deps: update dependency rimraf to v5.0.6 (04130f6)
deps: update dependency rimraf to v5.0.7 (c77a685)
deps: update dependency semantic-release to v23.1.1 (2129005)
deps: update pnpm to v8.15.8 (c40251f)

Build System

deps: lock file maintenance (2b0dd43)

Continuous Integration

deps: update actions/checkout action to v4.1.5 (726c6ce)
deps: update actions/checkout action to v4.1.6 (c469b8b)
deps: update renovate docker tag to v37.327.2 (a5a32e5)
deps: update renovate docker tag to v37.329.0 (80ac7b0)
deps: update renovate docker tag to v37.329.1 (c860f8b)
deps: update renovate docker tag to v37.330.0 (4ac1023)
deps: update renovate docker tag to v37.336.0 (c3a2a92)
deps: update renovate docker tag to v37.340.4 (a5c073e)
deps: update renovate docker tag to v37.340.5 (7c8209b)
deps: update renovate docker tag to v37.340.7 (#836) (c83cffd)
deps: update renovate docker tag to v37.340.8 (747a790)
deps: update renovate docker tag to v37.340.9 (9510584)
deps: update renovate docker tag to v37.342.1 (8370a32)
deps: update renovate docker tag to v37.347.0 (f30f9cd)
deps: update renovate docker tag to v37.349.2 (ccae59d)
deps: update renovate docker tag to v37.349.3 (c3f50f9)
deps: update renovate docker tag to v37.351.2 (5aa9fd4)
deps: update renovate docker tag to v37.353.0 (fc254a7)
deps: update renovate docker tag to v37.353.1 (32702b1)
deps: update renovate docker tag to v37.354.1 (64b8e78)
deps: update renovate docker tag to v37.354.6 (835916b)
deps: update renovate docker tag to v37.355.1 (fa66f0f)
deps: update renovate docker tag to v37.356.0 (f26bed6)
deps: update renovate docker tag to v37.356.1 (0cb6900)
deps: update renovate docker tag to v37.358.0 (8d0582d)
deps: update renovate docker tag to v37.363.9 (1bb8d42)
deps: update renovate docker tag to v37.368.1 (012ab12)
deps: update renovate docker tag to v37.368.6 (129d6fe)
deps: update renovate docker tag to v37.368.7 (f4404cb)
deps: update renovate docker tag to v37.368.9 (45e5900)
deps: update renovate docker tag to v37.371.1 (e966f22)
deps: update renovate docker tag to v37.374.3 (ed9467d)
deps: update renovate docker tag to v37.375.2 (a57ae60)
deps: update renovate docker tag to v37.377.0 (7cd9e62)
deps: update renovate docker tag to v37.377.2 (c5b906f)
deps: update renovate docker tag to v37.377.4 (11c642f)
deps: update renovate docker tag to v37.377.5 (6be22c7)
deps: update renovate docker tag to v37.377.6 (1c7d894)
deps: update renovate docker tag to v37.377.7 (eeb5134)
deps: update renovate docker tag to v37.377.8 (9d4b1c8)
deps: update renovate docker tag to v37.379.0 (72ad8b1)
deps: update renovate docker tag to v37.381.10 (16df9eb)
deps: update renovate docker tag to v37.381.2 (2fd6048)
deps: update renovate docker tag to v37.381.3 (2132b87)
deps: update renovate docker tag to v37.381.4 (30625d1)
deps: update renovate docker tag to v37.381.6 (8050d3a)
deps: update renovate docker tag to v37.381.7 (6723050)
deps: update renovate docker tag to v37.381.8 (fa4b235)
deps: update renovate docker tag to v37.381.9 (d51bce0)
deps: update renovate docker tag to v37.382.3 (a7244bf)
deps: update renovate docker tag to v37.382.4 (9672df0)
deps: update renovate docker tag to v37.384.0 (2499cb4)
deps: update renovate docker tag to v37.385.0 (40dc267)

svg/svgo (svgo)

`v3.3.2`

Compare Source

Notice

An update on what happened with v3.3.0 and v3.3.1. While we have retained CJS support, the migration to EMS has changed the acceptable ways to import SVGO, in ways that users depended on before. This effectively made SVGO v3 a breaking change.

Rather than resolve or workaround these differences, we've opted to release SVGO v3.3.2, which is effectively a revert to v3.2.0, and deprecate versions v3.3.0 and v3.3.1. We'll then proceed to work on releasing v4 which will document the breaking changes, and feature further breaking changes that were slated for v4, like disabling removeViewBox by default.

Before the v4.0.0 release, I'll put more focus on testing and use release candidates, just to help make the release go smoothly! 👍🏽

Sorry for the headache, and thanks for your patience.

`v3.3.1`

Compare Source

Notice

SVGO v3.3.0, which was meant to migrate to ESM without breaking CJS support, unfortunately broke CJS projects. There was a mistake with exports, so the loadConfig function wasn't available in the CJS bundle and lead to issues for many users.

Thanks to everyone who raised the issue, and to @nuintun who submitted a pull request to resolve it so quickly.

I apologize for letting that breaking change through, and will aim to do better. Namely, by adding more tests to cover our exports, and any other public interface in general for each distribution of SVGO, so this doesn't happen again.

SVGO v3.3.1 should resolve the issue for CJS projects, but if you encounter anything else, do let us know by opening an issue on GitHub.

`v3.3.0`

Compare Source

Deprecated

This release introduced breaking changes, which have been reverted in v3.3.2. The bug fixes will be reintroduced in v4.0.0.

What's Changed

ESM

SVGO is now a dual package, serving for both Common JS and ESM usage. We believe there shouldn't be any problems, especially as SVGO as largely stateless, but feel free to open an issue if you encounter problems with this.

To be explicit, this is not a breaking change, and SVGO should continue to work in Common JS projects!

Thanks to @jdufresne for doing the bulk of the work.

Default Behavior

convertColors, now converts all references to colors excluding references to IDs to lowercase. This can be disabled by setting convertCase to false.

Bug Fixes

cleanupIds, treat both URI encoded and non-URI encoded IDs as the same. By @liuweifeng in #1982
collapseGroups, check styles as well as attributes. By @johnkenny54 in #1952
collapseGroups, move attributes atomically. By @johnkenny54 in https://github.com/svg/svgo/pull/1930
convertPathData, fix q control point when item is removed. By @KTibow in https://github.com/svg/svgo/pull/1927
convertPathData, preserve vertex for markers only paths. By @SethFalco in #1967
mergePaths, don't merge paths if attributes/styles depend depend on the nodes bounding box. By @johnkenny54 in #1964
moveElemsAttrsToGroups, no longer moves the transforms if group has the filter attribute. By @johnkenny54 in #1933
prefixIds, fixed issue where some IDs were not prefixed when style tag contained XML comments. By @john-neptune in #1942
removeHiddenElems, don't remove node if child element has a referenced ID. By @johnkenny54 in https://github.com/svg/svgo/pull/1925
removeHiddenElems, treat path[opacity=0] as a non-rendering node. By @johnkenny54 in #1948
removeUselessDefs, don't remove node if child element has an ID. By @johnkenny54 in https://github.com/svg/svgo/pull/1923
When stringifying path data, include a space before numbers represented in scientific notation. By @johnkenny54 in #1961
No longer crashes when the output (-o argument) ends with a trailing slash to a location that didn't exist. By @SethFalco in #1954

SVG Optimization

convertColors, introduce parameter to convert colors to common casing (lowercase/uppercase). By @JayLeininger in https://github.com/svg/svgo/pull/1692
removeDeprecatedAttrs, new plugin that is disabled by default to remove SVG attributes that are deprecated. By @jdufresne in #1869

Metrics

Before and after using vectors from various sources, with the default preset of each respective version:

SVG	Original	v3.2.0	v3.3.0	Delta
Arch Linux Logo	9.529 KiB	4.115 KiB	4.097 KiB	⬇️ 0.018 KiB
Blobs	50.45 KiB	42.623 KiB	42.609 KiB	⬇️ 0.014 KiB
Isometric Madness	869.034 KiB	540.582 KiB	540.073 KiB	⬇️ 0.509 KiB
tldr-pages Banner	2.071 KiB	1.07 KiB	1.07 KiB
Wikipedia Logo	161.551 KiB	111.668 KiB	111.668 KiB

Before and after of the browser bundle of each respective version:

	v3.2.0	v3.3.0	Delta
svgo.browser.js	910.9 kB	753.0 kB	⬇️ 157.9 kB

Configuration

📅 Schedule: 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 has been generated by Mend Renovate. View repository job log here.

renovate bot added the dependencies label May 26, 2024

renovate bot force-pushed the renovate/all branch from 75299de to f9d9142 Compare June 1, 2024 08:39

Update all dependencies

09f3712

renovate bot force-pushed the renovate/all branch from f9d9142 to 09f3712 Compare June 4, 2024 05:12

renovate bot changed the title ~~Update all dependencies~~ Update all dependencies - autoclosed Jun 5, 2024

renovate bot closed this Jun 5, 2024

renovate bot deleted the renovate/all branch June 5, 2024 20:39

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Update all dependencies - autoclosed #2

Update all dependencies - autoclosed #2

renovate bot commented May 26, 2024 •

edited

Loading

Update all dependencies - autoclosed #2

Update all dependencies - autoclosed #2

Conversation

renovate bot commented May 26, 2024 • edited Loading

Release Notes

What's Changed

New Contributors

Documentation

Miscellaneous Chores

Build System

Continuous Integration

Notice

Notice

Deprecated

What's Changed

ESM

Default Behavior

Bug Fixes

SVG Optimization

Metrics

Configuration

renovate bot commented May 26, 2024 •

edited

Loading