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

renovate · 2024-05-09T05:51:35Z

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@angular-devkit/build-angular	`^17.3.6` -> `^17.3.7`
@angular/animations (source)	`~17.3.7` -> `~17.3.8`
@angular/cli	`~17.3.6` -> `~17.3.7`
@angular/common (source)	`~17.3.7` -> `~17.3.8`
@angular/compiler (source)	`~17.3.7` -> `~17.3.8`
@angular/compiler-cli (source)	`~17.3.7` -> `~17.3.8`
@angular/core (source)	`~17.3.7` -> `~17.3.8`
@angular/forms (source)	`~17.3.7` -> `~17.3.8`
@angular/platform-browser (source)	`~17.3.7` -> `~17.3.8`
@angular/platform-browser-dynamic (source)	`~17.3.7` -> `~17.3.8`
@angular/router (source)	`~17.3.7` -> `~17.3.8`
@types/node (source)	`^20.12.10` -> `^20.12.12`
@types/node (source)	`^20.12.10` -> `^20.12.12`
@types/react (source)	`^18.3.1` -> `^18.3.2`
@typescript-eslint/eslint-plugin (source)	`^7.8.0` -> `^7.9.0`
@typescript-eslint/parser (source)	`^7.8.0` -> `^7.9.0`
cypress (source)	`^13.8.1` -> `^13.9.0`
esbuild	`^0.21.0` -> `^0.21.2`
eslint-plugin-workspaces	`^0.10.0` -> `^0.10.1`
glob	`^10.3.12` -> `^10.3.15`
rimraf	`^5.0.5` -> `^5.0.7`
vue-tsc (source)	`^2.0.16` -> `^2.0.17`

Release Notes

angular/angular-cli (@angular-devkit/build-angular)

`v17.3.7`

Compare Source

angular/angular (@angular/animations)

`v17.3.8`

Compare Source

compiler

Commit	Type	Description
c21b459ba6	fix	add math elements to schema (#55631) (#55645)

core

Commit	Type	Description
3818436ebc	fix	don't schedule timer triggers on the server (#55605)

typescript-eslint/typescript-eslint (@typescript-eslint/eslint-plugin)

`v7.9.0`

Compare Source

🩹 Fixes

eslint-plugin: [explicit-function-return-types] fix false positive on default parameters

❤️ Thank You

Kirk Waiblinger
Sheetal Nandi
Vinccool96

You can read about our versioning strategy and releases on our website.

typescript-eslint/typescript-eslint (@typescript-eslint/parser)

`v7.9.0`

Compare Source

This was a version bump only for parser to align it with other projects, there were no code changes.

You can read about our versioning strategy and releases on our website.

cypress-io/cypress (cypress)

`v13.9.0`

Compare Source

Changelog: https://docs.cypress.io/guides/references/changelog#13-9-0

evanw/esbuild (esbuild)

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

joshuajaco/eslint-plugin-workspaces (eslint-plugin-workspaces)

`v0.10.1`

Compare Source

Fixed an issue where importing a local file with the same name as a workspace would be detected as a workspace import (https://github.com/joshuajaco/eslint-plugin-workspaces/issues/32)

isaacs/node-glob (glob)

isaacs/rimraf (rimraf)

`v5.0.7`

Compare Source

`v5.0.6`

Compare Source

vuejs/language-tools (vue-tsc)

`v2.0.17`

Compare Source

Features

language-core: add JSDod support for component (#2377)
language-core: add JSDoc support for script setup binding variables (#3409)
language-core: add class component support (#4354)
language-service: re-support scoped class links in template (#4357)
typescript-plugin: create script setup block when auto import if needed
typescript-plugin: add JSDoc support for events in template (#4365)
component-meta: add JSDoc tags support for events
language-core: support defineOptions (#4362) - Thanks @zhiyuanzmj

Bug Fixes

language-core: hover not working for intrinsic element event name
language-core: showing false declared but not used errors for functions used in v-on="{}" (#4333)
language-core: fix nameless event expression formatting
language-core: types imported in the <script setup> should not be used as a variable in template (#4353)
language-core: renaming classname within scoped not working (#4355)
language-core: <style> completions and html custom data completions not provided in some cases (#4092)
language-core: improve code action edits mapping fault tolerance
language-core: support defineModel for generic component (#4345) - Thanks @zhiyuanzmj
language-service: completion cannot trigger in SFC root
component-meta: forceUseTs options not working

Other Changes

Upgrade Volar from v2.2.0 to v2.2.2.
- fix(language-server): pass correct languageId when creating virtual code (https://github.com/volarjs/volar.js/issues/173)
- fix(typescript): additional completion not working in plugin (#4323)
Upgrade Volar services from v0.0.42 to v0.0.44.
- feat(typescript): code action edits respect editor formatting settings (https://github.com/volarjs/services/issues/30)
- fix(typescript): not being able to jump to shims module definition
- fix(typescript): allowTextChangesInNewFiles never true for embedded documents
- perf(typescript): check command resolve capability only for specific refactors (https://github.com/volarjs/services/issues/94)
The following extensions have been added to Hybrid Mode’s compatibility whitelist:
- mxsdev.typescript-explorer
Deprecated vueCompilerOptions.experimentalUseElementAccessInTemplate
Specify packageManager (#4358) - Thanks @so1ve
docs: emoved possibly redundant duplicate reference (#4348) - Thanks @artshade
language-service: temporarily remove references codeLens (#4364)
vscode: auto enabling hybrid mode allows

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 · 2024-05-09T05:51:37Z

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

any of the package files in this branch needs updating, or
the branch becomes conflicted, or
you click the rebase/retry checkbox if found above, or
you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: pnpm-lock.yaml

Scope: all 5 workspace projects
Progress: resolved 1, reused 0, downloaded 0, added 0
Progress: resolved 18, reused 0, downloaded 11, added 0
Progress: resolved 33, reused 0, downloaded 26, added 0
Progress: resolved 39, reused 0, downloaded 32, added 0
Progress: resolved 71, reused 0, downloaded 64, added 0
Progress: resolved 125, reused 0, downloaded 111, added 0
Progress: resolved 262, reused 0, downloaded 248, added 0
Progress: resolved 306, reused 0, downloaded 292, added 0
Progress: resolved 343, reused 0, downloaded 331, added 0
Progress: resolved 375, reused 0, downloaded 364, added 0
Progress: resolved 451, reused 0, downloaded 440, added 0
Progress: resolved 504, reused 0, downloaded 465, added 0
Progress: resolved 533, reused 0, downloaded 478, added 0
Progress: resolved 571, reused 0, downloaded 489, added 0
Progress: resolved 579, reused 0, downloaded 536, added 0
Progress: resolved 624, reused 0, downloaded 586, added 0
Progress: resolved 670, reused 0, downloaded 625, added 0
Progress: resolved 760, reused 0, downloaded 704, added 0
Progress: resolved 820, reused 0, downloaded 779, added 0
Progress: resolved 869, reused 0, downloaded 828, added 0
Progress: resolved 940, reused 0, downloaded 887, added 0
Progress: resolved 994, reused 0, downloaded 970, added 0
Progress: resolved 1059, reused 0, downloaded 1036, added 0
 ERR_PNPM_PATCH_NOT_APPLIED  The following patches were not applied: mockttp@3.10.2

Either remove them from "patchedDependencies" or update them to match packages in your dependencies.

renovate · 2024-05-09T15:06:07Z

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

any of the package files in this branch needs updating, or
the branch becomes conflicted, or
you click the rebase/retry checkbox if found above, or
you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: pnpm-lock.yaml

Scope: all 5 workspace projects
Progress: resolved 1, reused 0, downloaded 0, added 0
Progress: resolved 16, reused 0, downloaded 10, added 0
Progress: resolved 32, reused 0, downloaded 25, added 0
Progress: resolved 38, reused 0, downloaded 31, added 0
Progress: resolved 62, reused 0, downloaded 55, added 0
Progress: resolved 71, reused 0, downloaded 66, added 0
Progress: resolved 88, reused 0, downloaded 71, added 0
Progress: resolved 181, reused 0, downloaded 168, added 0
Progress: resolved 287, reused 0, downloaded 274, added 0
Progress: resolved 377, reused 0, downloaded 367, added 0
Progress: resolved 468, reused 0, downloaded 439, added 0
Progress: resolved 494, reused 0, downloaded 451, added 0
Progress: resolved 502, reused 0, downloaded 463, added 0
Progress: resolved 524, reused 0, downloaded 480, added 0
Progress: resolved 578, reused 0, downloaded 507, added 0
Progress: resolved 683, reused 0, downloaded 625, added 0
Progress: resolved 798, reused 0, downloaded 739, added 0
Progress: resolved 939, reused 0, downloaded 879, added 0
 ERR_PNPM_PATCH_NOT_APPLIED  The following patches were not applied: mockttp@3.10.2

Either remove them from "patchedDependencies" or update them to match packages in your dependencies.

renovate · 2024-05-14T13:49:48Z

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

renovate bot requested review from DreierF and stahlbauer May 9, 2024 05:51

renovate bot force-pushed the renovate/all-minor-patch-npm branch from 857dfcb to 69a0b31 Compare May 9, 2024 15:06

renovate bot force-pushed the renovate/all-minor-patch-npm branch 7 times, most recently from cdf70dd to cba306f Compare May 13, 2024 20:28

chore(deps): update all non-major npm dependencies

5705081

renovate bot force-pushed the renovate/all-minor-patch-npm branch from cba306f to 5705081 Compare May 14, 2024 07:36

TS-0 Mockttp upgrade

73b3f85

TS-0 Use Pnpm 9

6596d77

stahlbauer merged commit 0a8353b into master May 15, 2024
3 checks passed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

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

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

renovate bot commented May 9, 2024 •

edited

renovate bot commented May 9, 2024

renovate bot commented May 9, 2024 •

edited

renovate bot commented May 14, 2024

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

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

Conversation

renovate bot commented May 9, 2024 • edited

Release Notes

compiler

core

🩹 Fixes

❤️ Thank You

Features

Bug Fixes

Other Changes

Configuration

renovate bot commented May 9, 2024

⚠ Artifact update problem

File name: pnpm-lock.yaml

renovate bot commented May 9, 2024 • edited

⚠️ Artifact update problem

File name: pnpm-lock.yaml

renovate bot commented May 14, 2024

Edited/Blocked Notification

renovate bot commented May 9, 2024 •

edited

renovate bot commented May 9, 2024 •

edited