chore(deps): update all non-major dependencies #36

renovate · 2024-04-22T00:38:18Z

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@babel/types (source)	`^7.24.0` -> `^7.24.5`
@sxzz/eslint-config	`^3.9.1` -> `^3.11.0`
@types/node (source)	`^20.12.7` -> `^20.12.12`
bumpp	`^9.4.0` -> `^9.4.1`
esbuild	`^0.20.2` -> `^0.21.3`
eslint (source)	`^9.0.0` -> `^9.3.0`
magic-string-ast	`^0.5.0` -> `^0.6.1`
pnpm (source)	`9.0.1` -> `9.1.2`
rollup (source)	`^4.14.3` -> `^4.18.0`
tsx	`^4.7.2` -> `^4.11.0`
vite (source)	`^5.2.9` -> `^5.2.11`
vite-node (source)	`^1.5.0` -> `^1.6.0`
vitest (source)	`^1.5.0` -> `^1.6.0`
vue (source)	`^3.4.23` -> `^3.4.27`

Release Notes

babel/babel (@babel/types)

`v7.24.5`

Compare Source

🐛 Bug Fix

babel-plugin-transform-classes, babel-traverse
- #16377 fix: TypeScript annotation affects output (@liuxingbaoyu)
babel-helpers, babel-plugin-proposal-explicit-resource-management, babel-runtime-corejs3
- #16440 Fix suppressed error order (@sossost)
- #16408 Await nullish async disposable (@JLHwung)

💅 Polish

babel-parser
- #16407 Recover from exported using declaration (@JLHwung)

🏠 Internal

Other
- #16414 Relax ESLint peerDependency constraint to allow v9 (@liuxingbaoyu)
babel-parser
- #16425 Improve @babel/parser AST types (@nicolo-ribaudo)
- #16417 Always pass type argument to .startNode (@nicolo-ribaudo)
babel-helper-create-class-features-plugin, babel-helper-member-expression-to-functions, babel-helper-module-transforms, babel-helper-split-export-declaration, babel-helper-wrap-function, babel-helpers, babel-plugin-bugfix-firefox-class-in-computed-class-key, babel-plugin-proposal-explicit-resource-management, babel-plugin-transform-block-scoping, babel-plugin-transform-destructuring, babel-plugin-transform-object-rest-spread, babel-plugin-transform-optional-chaining, babel-plugin-transform-parameters, babel-plugin-transform-private-property-in-object, babel-plugin-transform-react-jsx-self, babel-plugin-transform-typeof-symbol, babel-plugin-transform-typescript, babel-traverse
- #16439 Make NodePath<T | U> distributive (@nicolo-ribaudo)
babel-plugin-proposal-partial-application, babel-types
- #16421 Remove JSXNamespacedName from valid CallExpression args (@nicolo-ribaudo)
babel-plugin-transform-class-properties, babel-preset-env
- #16406 Do not load unnecessary Babel 7 syntax plugins in Babel 8 (@nicolo-ribaudo)

🏃‍♀️ Performance

babel-helpers, babel-preset-env, babel-runtime-corejs3
- #16357 Performance: improve objectWithoutPropertiesLoose on V8 (@romgrk)

sxzz/eslint-config (@sxzz/eslint-config)

`v3.11.0`

Compare Source

🚀 Features

Add eslint-plugin-command - by @sxzz (43efe)

View changes on GitHub

`v3.10.1`

Compare Source

🐞 Bug Fixes

Disable some unicron rules - by @sxzz (e6985)

View changes on GitHub

`v3.10.0`

Compare Source

🚨 Breaking Changes

Drop cjs package - by @sxzz (50628)

🐞 Bug Fixes

deps:
- Update dependency eslint-plugin-n to v17 - by @renovate[bot] inhttps://github.com/sxzz/eslint-config/issues/744 (75096)
- Update dependency eslint-plugin-markdown to v5 - by @renovate[bot] inhttps://github.com/sxzz/eslint-config/issues/766 (7fc96)

View changes on GitHub

antfu/bumpp (bumpp)

`v9.4.1`

Compare Source

evanw/esbuild (esbuild)

`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() {}
```

eslint/eslint (eslint)

sxzz/magic-string-ast (magic-string-ast)

`v0.6.1`

Compare Source

No significant changes

View changes on GitHub

`v0.6.0`

Compare Source

🚀 Features

Compatible with magic-string-stack - by @sxzz (310f6)

View changes on GitHub

pnpm/pnpm (pnpm)

`v9.1.2`

Compare Source

`v9.1.1`

Compare Source

`v9.1.0`

Compare Source

`v9.0.6`

Compare Source

`v9.0.5`

Compare Source

`v9.0.4`

Compare Source

`v9.0.3`

Compare Source

`v9.0.2`

Compare Source

rollup/rollup (rollup)

`v4.18.0`

Compare Source

2024-05-22

Features

Resolve import.meta.filename and .dirname in transpiled plugins (#5520)

Pull Requests

#5504: Auto generate node index (@lukastaegert)
#5507: chore(deps): lock file maintenance minor/patch updates (@renovate[bot])
#5508: chore(deps): lock file maintenance (@renovate[bot])
#5510: Split up converter.rs into AST nodes (@lukastaegert)
#5512: chore(deps): update dependency builtin-modules to v4 (@renovate[bot], @lukastaegert)
#5514: chore(deps): lock file maintenance minor/patch updates (@renovate[bot])
#5518: chore(deps): update dependency eslint-plugin-unicorn to v53 (@renovate[bot], @lukastaegert)
#5519: chore(deps): lock file maintenance minor/patch updates (@renovate[bot], @lukastaegert)
#5520: Resolve import.meta.{filename,dirname} in files imported from config (@BPScott)
#5521: docs: correct base32 to base36 in documentation (@highcastlee)

`v4.17.2`

Compare Source

2024-04-30

Bug Fixes

Fix tree-shaking problems when using spread arguments (#5503)

Pull Requests

#5501: Slightly improve perf report (@lukastaegert)
#5503: fix: rest element should deoptimize parameter values (@liuly0322)

`v4.17.1`

Compare Source

2024-04-29

Bug Fixes

Prevent infinite recursions for certain constructor invocations (#5500)

Pull Requests

#5500: fix: parameter variable infinite recursion error (@liuly0322)

`v4.17.0`

Compare Source

2024-04-27

Features

Track function call arguments to optimize functions only called once or with the same literal values (re-release from 4.16.0) (#5483)

Bug Fixes

Reduce browser WASM size to a fraction by changing optimization settings (#5494)

Pull Requests

#5483: feature(fix): function parameter tracking (@liuly0322)
#5488: Report performance in CI (@TrickyPi)
#5489: Create FUNDING.json (@BenJam)
#5492: chore(deps): lock file maintenance minor/patch updates (@renovate[bot])
#5493: chore(deps): lock file maintenance minor/patch updates (@renovate[bot])
#5494: Use opt-level=z for browser wasm (@sapphi-red)

`v4.16.4`

Compare Source

2024-04-23

Bug Fixes

Revert function parameter tracking logic introduced in 4.16.0 to work on some remaining issues (#5487)

Pull Requests

#5487: Revert function parameter tracking logic for now (@lukastaegert)

`v4.16.3`

Compare Source

2024-04-23

Bug Fixes

Do not optimize IIFEs that have a name and are again referenced inside their definition (#5486)

Pull Requests

#5486: fix: only optimize annoymous iife (@liuly0322)

`v4.16.2`

Compare Source

2024-04-22

Bug Fixes

Resolve a situation condition where reassignments of function parameters were not tracked properly (#5482)
Make sure that for armv7 packages, only one package is downloaded for the user (musl or gnu) (#5479)

Pull Requests

#5479: Add libc field to armv7 packages (@sapphi-red)
#5482: fix: function parameter reassigned update (@liuly0322)

`v4.16.1`

Compare Source

2024-04-21

Bug Fixes

Fix crash when rendering logical or conditional expressions (#5481)

Pull Requests

#5481: fix: conditional/logical expression should request a new tree-shaking (@liuly0322)

`v4.16.0`

Compare Source

2024-04-21

Features

Track function call arguments to optimize functions only called once or with the same literal values (#5443)

Pull Requests

#5443: feat: improve tree-shaking by propagate const parameter (@liuly0322, @lukastaegert)

`v4.15.0`

Compare Source

2024-04-20

Features

Add output.importAttributesKey option to select whether to use "with" or "assert" for import attributes (#5474)

Pull Requests

#5474: Add ImportAttributesKey to choose keyword ("with" | "assert") (@doubleaa93, @lukastaegert)
#5475: chore(deps): lock file maintenance minor/patch updates (@renovate[bot])
#5477: Try to run emulated smoke tests for Linux environments (@lukastaegert)

privatenumber/tsx (tsx)

`v4.11.0`

Compare Source

Bug Fixes

only error on invalid tsconfig if explicitly passed in (#30) (b6bf39b)

Features

esm api: configurable tsconfig (3f42ae3)

This release is also available on:

npm package (@latest dist-tag)

`v4.10.5`

Compare Source

Bug Fixes

handle parsing variable of (86cf87c), closes #556

This release is also available on:

npm package (@latest dist-tag)

`v4.10.4`

Compare Source

`v4.10.3`

Compare Source

Performance Improvements

skip parsing if import( is not found in minified code (5cdd50b)

This release is also available on:

npm package (@latest dist-tag)

`v4.10.2`

Compare Source

`v4.10.1`

Compare Source

`v4.10.0`

Compare Source

Features

esm api: register to return a namespaced import() method (53bb4aa)

This release is also available on:

npm package (@latest dist-tag)

`v4.9.5`

Compare Source

`v4.9.4`

Compare Source

Bug Fixes

tsImport: import module from commonjs (48f0a75)

This release is also available on:

npm package (@latest dist-tag)

`v4.9.3`

Compare Source

Bug Fixes

import implicit extensions from packages (8022fcf), closes #542

This release is also available on:

npm package (@latest dist-tag)

`v4.9.2`

Compare Source

Bug Fixes

esm: resolve absolute paths (#544) (3a0ea18)

This release is also available on:

npm package (@latest dist-tag)

`v4.9.1`

Compare Source

`v4.9.0`

Compare Source

`v4.8.2`

Compare Source

Bug Fixes

types: cjs/api to use .d.cts (4b1f03c)

This release is also available on:

npm package (@latest dist-tag)

`v4.8.1`

Compare Source

`v4.8.0`

Compare Source

`v4.7.3`

Compare Source

Bug Fixes

support TS resolution in JS files when allowJs is set (#535) (081853e)

This release is also available on:

npm package (@latest dist-tag)

vitejs/vite (vite)

`v5.2.11`

Compare Source

feat: improve dynamic import variable failure error message (#16519) (f8feeea), closes #16519
fix: dynamic-import-vars plugin normalize path issue (#16518) (f71ba5b), closes #16518
fix: scripts and styles were missing from built HTML on Windows (#16421) (0e93f58), closes #16421
fix(deps): update all non-major dependencies (#16488) (2d50be2), closes #16488
fix(deps): update all non-major dependencies (#16549) (2d6a13b), closes #16549
fix(dev): watch publicDir explicitly to include it outside the root (#16502) (4d83eb5), closes #16502
fix(preload): skip preload for non-static urls (#16556) (bb79c9b), closes #16556
fix(ssr): handle class declaration and expression name scoping (#16569) (c071eb3), closes #16569
fix(ssr): handle function expression name scoping (#16563) (02db947), closes #16563

`v5.2.10`

Compare Source

revert: perf: use workspace root for fs cache (#15712) (#16476) (77e7359), closes #15712 #16476
fix: add base to virtual html (#16442) (721f94d), closes #16442
fix: adjust esm syntax judgment logic (#16436) (af72eab), closes #16436
fix: don't add outDirs to watch.ignored if emptyOutDir is false (#16453) (6a127d6), closes #16453
fix(cspNonce): don't overwrite existing nonce values (#16415) (b872635), closes #16415
feat: show warning if root is in build.outDir (#16454) (11444dc), closes #16454
feat: write cspNonce to style tags (#16419) (8e54bbd), closes #16419
chore(deps): update dependency eslint-plugin-n to v17 (#16381) (6cccef7), closes #16381

vitest-dev/vitest (vite-node)

`v1.6.0`

Compare Source

🚀 Features

Support standalone mode - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/5565 (bdce0)
Custom "snapshotEnvironment" option - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/5449 (30f72)
benchmark: Support comparing benchmark result - by @hi-ogawa and @sheremet-va in https://github.com/vitest-dev/vitest/issues/5398 (f8d3d)
browser: Allow injecting scripts - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/5656 (21e58)
reporter: Support includeConsoleOutput and addFileAttribute in junit - by @hi-ogawa in https://github.com/vitest-dev/vitest/issues/5659 (2f913)
ui: Sort items by file name - by @btea in https://github.com/vitest-dev/vitest/issues/5652 (1f726)

🐞 Bug Fixes

Keep order of arguments for .each in custom task collectors - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/5640 (7d57c)
Call resolveId('vitest') after buildStart - by @hi-ogawa in https://github.com/vitest-dev/vitest/issues/5646 (f5faf)
Hash the name of the file when caching - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/5654 (c9e68)
Don't panic on empty files in node_modules - by @sheremet-va (40c29)
Use toJSON for error serialization - by @hi-ogawa in https://github.com/vitest-dev/vitest/issues/5526 (19a21)
coverage:
- Exclude *.test-d.* by default - by @MindfulPol in https://github.com/vitest-dev/vitest/issues/5634 (bfe8a)
- Apply vite-node's wrapper only to executed files - by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/5642 (c9883)
vm:
- Support network imports - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/5610 (103a6)

🏎 Performance

Improve performance of forks pool - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/5592 [(d8304)](https

Configuration

📅 Schedule: Branch creation - "before 4am on Monday" (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 has been generated by Mend Renovate. View repository job log here.

stackblitz · 2024-04-22T00:38:21Z

Run & review this pull request in StackBlitz Codeflow.

socket-security · 2024-04-29T21:53:07Z

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/magic-string-ast@0.6.1	None	`+2`	511 kB	sxzz

🚮 Removed packages: npm/magic-string-ast@0.5.0

View full report↗︎

renovate bot added the dependencies label Apr 22, 2024

renovate bot force-pushed the renovate/all-minor-patch branch 9 times, most recently from 0d80e46 to 918e221 Compare April 29, 2024 11:36

renovate bot force-pushed the renovate/all-minor-patch branch from 918e221 to ab1fea3 Compare April 29, 2024 21:46

renovate bot force-pushed the renovate/all-minor-patch branch 16 times, most recently from dd69b00 to 17987a3 Compare May 7, 2024 04:47

renovate bot force-pushed the renovate/all-minor-patch branch from 17987a3 to 2650d26 Compare May 7, 2024 18:27

renovate bot force-pushed the renovate/all-minor-patch branch 9 times, most recently from e7d39fe to b45202b Compare May 14, 2024 06:18

renovate bot force-pushed the renovate/all-minor-patch branch 7 times, most recently from 7cd534b to faa0a45 Compare May 22, 2024 12:36

chore(deps): update all non-major dependencies

3eb9bed

renovate bot force-pushed the renovate/all-minor-patch branch from faa0a45 to 3eb9bed Compare May 23, 2024 06:04

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

chore(deps): update all non-major dependencies #36

chore(deps): update all non-major dependencies #36

renovate bot commented Apr 22, 2024 •

edited

stackblitz bot commented Apr 22, 2024

socket-security bot commented Apr 29, 2024 •

edited

chore(deps): update all non-major dependencies #36

Are you sure you want to change the base?

chore(deps): update all non-major dependencies #36

Conversation

renovate bot commented Apr 22, 2024 • edited

Release Notes

🐛 Bug Fix

💅 Polish

🏠 Internal

🏃‍♀️ Performance

🚀 Features

🐞 Bug Fixes

🚨 Breaking Changes

🐞 Bug Fixes

🚀 Features

Features

Pull Requests

Bug Fixes

Pull Requests

Bug Fixes

Pull Requests

Features

Bug Fixes

Pull Requests

Bug Fixes

Pull Requests

Bug Fixes

Pull Requests

Bug Fixes

Pull Requests

Bug Fixes

Pull Requests

Features

Pull Requests

Features

Pull Requests

Bug Fixes

Features

Bug Fixes

Performance Improvements

Features

Bug Fixes

Bug Fixes

Bug Fixes

Bug Fixes

Bug Fixes

🚀 Features

🐞 Bug Fixes

🏎 Performance

Configuration

stackblitz bot commented Apr 22, 2024

socket-security bot commented Apr 29, 2024 • edited

renovate bot commented Apr 22, 2024 •

edited

socket-security bot commented Apr 29, 2024 •

edited