vikunja
/
vikunja
6
43
Fork 72
Code Issues 150 Pull Requests 19 Packages Releases 32 Activity

chore(deps): update dev-dependencies #2330

Merged
konrad merged 1 commits from renovate/dev-dependencies into main 2024-05-07 08:04:51 +00:00
Conversation 1 Commits 1 Files Changed 2 +320 -82
renovate commented 2024-05-07 00:06:06 +00:00
Member
Copy Link

This PR contains the following updates:

Package Type Update Change
@types/node (source) devDependencies patch 20.12.8 -> 20.12.10
@vue/test-utils devDependencies patch 2.4.5 -> 2.4.6
esbuild devDependencies minor 0.20.2 -> 0.21.0
happy-dom devDependencies minor 14.7.1 -> 14.10.1
sass devDependencies minor 1.76.0 -> 1.77.0

Release Notes

vuejs/test-utils (@​vue/test-utils)

v2.4.6

Compare Source

What's Changed

New Contributors

Full Changelog: https://github.com/vuejs/test-utils/compare/v2.4.5...v2.4.6

evanw/esbuild (esbuild)

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 {
  @​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() {}
capricorn86/happy-dom (happy-dom)

v14.10.1

Compare Source

👷‍♂️ Patch fixes
  • Makes descriptor for properties "configurable" to make Storage.entries(), Storage.keys() and Storage.values() work according to spec - By @​motss in task #​1418

v14.10.0

Compare Source

🎨 Features
  • Adds support for Document.elementFromPoint() - By @​TreyVigus in task #​1400
    • The method will always return null as Happy DOM doesn't support rendering and can't calculate an element's position based on where it is rendered

v14.9.0

Compare Source

🎨 Features
  • Adds support for Document.queryCommandSupported() - By @​btea in task #​1411

v14.8.3

Compare Source

👷‍♂️ Patch fixes
  • Fixes issue related to Element.insertBefore() not removing comment node from previous ancestor - By @​mdafanasev in task #​1406

v14.8.2

Compare Source

👷‍♂️ Patch fixes
  • Changes implementation to return HTMLCollection instead of NodeList in Document.forms - By @​jean-leonco in task #​1349

v14.8.1

Compare Source

👷‍♂️ Patch fixes

v14.8.0

Compare Source

🎨 Features
sass/dart-sass (sass)

v1.77.0

Compare Source

  • Don't throw errors for at-rules in keyframe blocks.

Configuration

📅 Schedule: Branch creation - "before 4am" (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 Renovate Bot.

This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | [@types/node](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/node) ([source](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/node)) | devDependencies | patch | [`20.12.8` -> `20.12.10`](https://renovatebot.com/diffs/npm/@types%2fnode/20.12.8/20.12.10) | | [@vue/test-utils](https://github.com/vuejs/test-utils) | devDependencies | patch | [`2.4.5` -> `2.4.6`](https://renovatebot.com/diffs/npm/@vue%2ftest-utils/2.4.5/2.4.6) | | [esbuild](https://github.com/evanw/esbuild) | devDependencies | minor | [`0.20.2` -> `0.21.0`](https://renovatebot.com/diffs/npm/esbuild/0.20.2/0.21.0) | | [happy-dom](https://github.com/capricorn86/happy-dom) | devDependencies | minor | [`14.7.1` -> `14.10.1`](https://renovatebot.com/diffs/npm/happy-dom/14.7.1/14.10.1) | | [sass](https://github.com/sass/dart-sass) | devDependencies | minor | [`1.76.0` -> `1.77.0`](https://renovatebot.com/diffs/npm/sass/1.76.0/1.77.0) | --- ### Release Notes <details> <summary>vuejs/test-utils (@&#8203;vue/test-utils)</summary> ### [`v2.4.6`](https://github.com/vuejs/test-utils/releases/tag/v2.4.6) [Compare Source](https://github.com/vuejs/test-utils/compare/v2.4.5...v2.4.6) #### What's Changed - Fix/circular references in props cause maximum call stack size exceeded by [@&#8203;Evobaso-J](https://github.com/Evobaso-J) in https://github.com/vuejs/test-utils/pull/2371 - chore(deps): update all non-major dependencies by [@&#8203;renovate](https://github.com/renovate) in https://github.com/vuejs/test-utils/pull/2374 - docs: setup the translation helper by [@&#8203;Jinjiang](https://github.com/Jinjiang) in https://github.com/vuejs/test-utils/pull/2373 - chore: translate translation sync message in french by [@&#8203;cexbrayat](https://github.com/cexbrayat) in https://github.com/vuejs/test-utils/pull/2377 - docs: synchronize the french docs by [@&#8203;cexbrayat](https://github.com/cexbrayat) in https://github.com/vuejs/test-utils/pull/2378 - chore(deps): update dependency vite to v5.2.2 by [@&#8203;renovate](https://github.com/renovate) in https://github.com/vuejs/test-utils/pull/2376 - chore(deps): pin dependency vitepress-translation-helper to 0.1.3 by [@&#8203;renovate](https://github.com/renovate) in https://github.com/vuejs/test-utils/pull/2379 - chore(deps): update dependency typescript to v5.4.3 by [@&#8203;renovate](https://github.com/renovate) in https://github.com/vuejs/test-utils/pull/2380 - chore(deps): update dependency vitepress-translation-helper to v0.2.0 by [@&#8203;renovate](https://github.com/renovate) in https://github.com/vuejs/test-utils/pull/2381 - chore: update vitepress-translation-helper by [@&#8203;Jinjiang](https://github.com/Jinjiang) in https://github.com/vuejs/test-utils/pull/2382 - chore(deps): update dependency vitepress to v1.0.0 by [@&#8203;renovate](https://github.com/renovate) in https://github.com/vuejs/test-utils/pull/2383 - chore(deps): update dependency vitepress-translation-helper to v0.2.1 by [@&#8203;renovate](https://github.com/renovate) in https://github.com/vuejs/test-utils/pull/2384 - fix: update attachTo type in MountingOptions interface by [@&#8203;taku-y-9308](https://github.com/taku-y-9308) in https://github.com/vuejs/test-utils/pull/2375 - chore(deps): update all non-major dependencies by [@&#8203;renovate](https://github.com/renovate) in https://github.com/vuejs/test-utils/pull/2388 - docs(api): fix typo in attachTo anchor tag within isVisible by [@&#8203;matusekma](https://github.com/matusekma) in https://github.com/vuejs/test-utils/pull/2351 - change vm to always provide global property by [@&#8203;taku-y-9308](https://github.com/taku-y-9308) in https://github.com/vuejs/test-utils/pull/2386 - chore(deps): update dependency rollup to v4.13.1 by [@&#8203;renovate](https://github.com/renovate) in https://github.com/vuejs/test-utils/pull/2389 - chore(deps): update dependency reflect-metadata to v0.2.2 by [@&#8203;renovate](https://github.com/renovate) in https://github.com/vuejs/test-utils/pull/2391 - chore(deps): update all non-major dependencies by [@&#8203;renovate](https://github.com/renovate) in https://github.com/vuejs/test-utils/pull/2393 - chore(deps): update dependency vite to v5.2.8 by [@&#8203;renovate](https://github.com/renovate) in https://github.com/vuejs/test-utils/pull/2396 - docs: fix missing equal sign by [@&#8203;w2xi](https://github.com/w2xi) in https://github.com/vuejs/test-utils/pull/2398 - fix: renderStubDefaultSlot with scoped slots by [@&#8203;cexbrayat](https://github.com/cexbrayat) in https://github.com/vuejs/test-utils/pull/2397 - docs(api): fix missing chars by [@&#8203;w2xi](https://github.com/w2xi) in https://github.com/vuejs/test-utils/pull/2399 - docs: use innerHTML in teleport cleanup by [@&#8203;brc-dd](https://github.com/brc-dd) in https://github.com/vuejs/test-utils/pull/2403 - feat: Added dynamic return for element getter by [@&#8203;nandi95](https://github.com/nandi95) in https://github.com/vuejs/test-utils/pull/2406 - chore(deps): update all non-major dependencies by [@&#8203;renovate](https://github.com/renovate) in https://github.com/vuejs/test-utils/pull/2407 - chore(deps): update all non-major dependencies by [@&#8203;renovate](https://github.com/renovate) in https://github.com/vuejs/test-utils/pull/2408 - doc(api): fix missing char by [@&#8203;w2xi](https://github.com/w2xi) in https://github.com/vuejs/test-utils/pull/2410 - chore(deps): update all non-major dependencies by [@&#8203;renovate](https://github.com/renovate) in https://github.com/vuejs/test-utils/pull/2412 - chore: use node v18 on netlify by [@&#8203;cexbrayat](https://github.com/cexbrayat) in https://github.com/vuejs/test-utils/pull/2416 - fix(stubs): avoid warning on normalized props with Vue v3.4.22 by [@&#8203;cexbrayat](https://github.com/cexbrayat) in https://github.com/vuejs/test-utils/pull/2413 - chore: use the packageManager field from package.json in github action by [@&#8203;cexbrayat](https://github.com/cexbrayat) in https://github.com/vuejs/test-utils/pull/2417 - chore(deps): update pnpm to v9 by [@&#8203;renovate](https://github.com/renovate) in https://github.com/vuejs/test-utils/pull/2415 - chore(deps): update all non-major dependencies to v3.4.23 by [@&#8203;renovate](https://github.com/renovate) in https://github.com/vuejs/test-utils/pull/2418 - chore(deps): update all non-major dependencies by [@&#8203;renovate](https://github.com/renovate) in https://github.com/vuejs/test-utils/pull/2419 - chore(deps): update all non-major dependencies by [@&#8203;renovate](https://github.com/renovate) in https://github.com/vuejs/test-utils/pull/2420 - chore(deps): update all non-major dependencies by [@&#8203;renovate](https://github.com/renovate) in https://github.com/vuejs/test-utils/pull/2421 - Update index.md to fix typo and clarify `get` vs `find` behavior by [@&#8203;KatWorkGit](https://github.com/KatWorkGit) in https://github.com/vuejs/test-utils/pull/2422 - fix: set global provides before running vue plugins by [@&#8203;danielroe](https://github.com/danielroe) in https://github.com/vuejs/test-utils/pull/2423 - ci: add build on node v22 by [@&#8203;cexbrayat](https://github.com/cexbrayat) in https://github.com/vuejs/test-utils/pull/2424 - chore(deps): update all non-major dependencies by [@&#8203;renovate](https://github.com/renovate) in https://github.com/vuejs/test-utils/pull/2426 - chore(deps): update dependency unplugin-vue-components to v0.27.0 by [@&#8203;renovate](https://github.com/renovate) in https://github.com/vuejs/test-utils/pull/2427 - chore(deps): update dependency [@&#8203;types/node](https://github.com/types/node) to v20.12.8 by [@&#8203;renovate](https://github.com/renovate) in https://github.com/vuejs/test-utils/pull/2429 - Fix/issue 2319 throw first error thrown during mount by [@&#8203;taku-y-9308](https://github.com/taku-y-9308) in https://github.com/vuejs/test-utils/pull/2428 #### New Contributors - [@&#8203;Jinjiang](https://github.com/Jinjiang) made their first contribution in https://github.com/vuejs/test-utils/pull/2373 - [@&#8203;taku-y-9308](https://github.com/taku-y-9308) made their first contribution in https://github.com/vuejs/test-utils/pull/2375 - [@&#8203;matusekma](https://github.com/matusekma) made their first contribution in https://github.com/vuejs/test-utils/pull/2351 - [@&#8203;w2xi](https://github.com/w2xi) made their first contribution in https://github.com/vuejs/test-utils/pull/2398 - [@&#8203;brc-dd](https://github.com/brc-dd) made their first contribution in https://github.com/vuejs/test-utils/pull/2403 - [@&#8203;KatWorkGit](https://github.com/KatWorkGit) made their first contribution in https://github.com/vuejs/test-utils/pull/2422 **Full Changelog**: https://github.com/vuejs/test-utils/compare/v2.4.5...v2.4.6 </details> <details> <summary>evanw/esbuild (esbuild)</summary> ### [`v0.21.0`](https://github.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#0210) [Compare Source](https://github.com/evanw/esbuild/compare/v0.20.2...v0.21.0) 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 ([#&#8203;104](https://github.com/evanw/esbuild/issues/104)) With this release, esbuild now contains an implementation of the upcoming [JavaScript decorators proposal](https://github.com/tc39/proposal-decorators). This is the same feature that shipped in [TypeScript 5.0](https://devblogs.microsoft.com/typescript/announcing-typescript-5-0/#decorators) 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: ```js 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: ```js 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: ```js // 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()`: ```js 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: ```js 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: ```js // 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](https://tc39.es/ecma262/#sec-runtime-semantics-namedevaluation) 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: ```js 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: ```js 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() {} ``` </details> <details> <summary>capricorn86/happy-dom (happy-dom)</summary> ### [`v14.10.1`](https://github.com/capricorn86/happy-dom/releases/tag/v14.10.1) [Compare Source](https://github.com/capricorn86/happy-dom/compare/v14.10.0...v14.10.1) ##### :construction_worker_man: Patch fixes - Makes descriptor for properties "configurable" to make `Storage.entries()`, `Storage.keys()` and `Storage.values()` work according to spec - By **[@&#8203;motss](https://github.com/motss)** in task [#&#8203;1418](https://github.com/capricorn86/happy-dom/issues/1418) ### [`v14.10.0`](https://github.com/capricorn86/happy-dom/releases/tag/v14.10.0) [Compare Source](https://github.com/capricorn86/happy-dom/compare/v14.9.0...v14.10.0) ##### :art: Features - Adds support for `Document.elementFromPoint()` - By **[@&#8203;TreyVigus](https://github.com/TreyVigus)** in task [#&#8203;1400](https://github.com/capricorn86/happy-dom/issues/1400) - The method will always return `null` as Happy DOM doesn't support rendering and can't calculate an element's position based on where it is rendered ### [`v14.9.0`](https://github.com/capricorn86/happy-dom/releases/tag/v14.9.0) [Compare Source](https://github.com/capricorn86/happy-dom/compare/v14.8.3...v14.9.0) ##### :art: Features - Adds support for `Document.queryCommandSupported()` - By **[@&#8203;btea](https://github.com/btea)** in task [#&#8203;1411](https://github.com/capricorn86/happy-dom/issues/1411) ### [`v14.8.3`](https://github.com/capricorn86/happy-dom/releases/tag/v14.8.3) [Compare Source](https://github.com/capricorn86/happy-dom/compare/v14.8.2...v14.8.3) ##### :construction_worker_man: Patch fixes - Fixes issue related to `Element.insertBefore()` not removing comment node from previous ancestor - By **[@&#8203;mdafanasev](https://github.com/mdafanasev)** in task [#&#8203;1406](https://github.com/capricorn86/happy-dom/issues/1406) ### [`v14.8.2`](https://github.com/capricorn86/happy-dom/releases/tag/v14.8.2) [Compare Source](https://github.com/capricorn86/happy-dom/compare/v14.8.1...v14.8.2) ##### :construction_worker_man: Patch fixes - Changes implementation to return `HTMLCollection` instead of `NodeList` in `Document.forms` - By **[@&#8203;jean-leonco](https://github.com/jean-leonco)** in task [#&#8203;1349](https://github.com/capricorn86/happy-dom/issues/1349) ### [`v14.8.1`](https://github.com/capricorn86/happy-dom/releases/tag/v14.8.1) [Compare Source](https://github.com/capricorn86/happy-dom/compare/v14.8.0...v14.8.1) ##### :construction_worker_man: Patch fixes - Improves support of the `DOMRect` interface - By **[@&#8203;domakas](https://github.com/domakas)** in task [#&#8203;1161](https://github.com/capricorn86/happy-dom/issues/1161) - Adds support for the `DOMReactReadOnly` interface - By **[@&#8203;domakas](https://github.com/domakas)** in task [#&#8203;1161](https://github.com/capricorn86/happy-dom/issues/1161) ### [`v14.8.0`](https://github.com/capricorn86/happy-dom/releases/tag/v14.8.0) [Compare Source](https://github.com/capricorn86/happy-dom/compare/v14.7.1...v14.8.0) ##### :art: Features - Adds support for the `HTMLIFrameElement.srcdoc` property - By **[@&#8203;jeffwcx](https://github.com/jeffwcx)** in task [#&#8203;1398](https://github.com/capricorn86/happy-dom/issues/1398) </details> <details> <summary>sass/dart-sass (sass)</summary> ### [`v1.77.0`](https://github.com/sass/dart-sass/blob/HEAD/CHANGELOG.md#1770) [Compare Source](https://github.com/sass/dart-sass/compare/1.76.0...1.77.0) - *Don't* throw errors for at-rules in keyframe blocks. </details> --- ### Configuration 📅 **Schedule**: Branch creation - "before 4am" (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](https://github.com/renovatebot/renovate/discussions) if that's undesired. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzNy4zMjEuMiIsInVwZGF0ZWRJblZlciI6IjM3LjMyMS4yIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6WyJkZXBlbmRlbmNpZXMiXX0=-->
renovate added the
dependencies
 label 2024-05-07 00:06:06 +00:00
renovate added 1 commit 2024-05-07 00:06:08 +00:00
continuous-integration/drone/pr Build is passing Details
52d8e6ce73 chore(deps): update dev-dependencies
frederick commented 2024-05-07 00:14:17 +00:00
Member
Copy Link

Hi renovate!

Thank you for creating a PR!

I've deployed the frontend changes of this PR on a preview environment under this URL: https://2330-renovate-dev-dependencies--vikunja-frontend-preview.netlify.app

You can use this url to view the changes live and test them out.
You will need to manually connect this to an api running somewhere. The easiest to use is https://try.vikunja.io/.

This preview does not contain any changes made to the api, only the frontend.

Have a nice day!

Beep boop, I'm a bot.

Hi renovate! Thank you for creating a PR! I've deployed the frontend changes of this PR on a preview environment under this URL: https://2330-renovate-dev-dependencies--vikunja-frontend-preview.netlify.app You can use this url to view the changes live and test them out. You will need to manually connect this to an api running somewhere. The easiest to use is https://try.vikunja.io/. This preview does not contain any changes made to the api, only the frontend. Have a nice day! > Beep boop, I'm a bot.
renovate force-pushed renovate/dev-dependencies from 52d8e6ce73 to 1b53d07762 2024-05-07 01:06:08 +00:00 Compare
renovate force-pushed renovate/dev-dependencies from 1b53d07762 to e58d10bc72 2024-05-07 03:05:54 +00:00 Compare
konrad merged commit e58d10bc72 into main 2024-05-07 08:04:51 +00:00
konrad deleted branch renovate/dev-dependencies 2024-05-07 08:04:51 +00:00
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels   
dependencies

   
duplicate

This issue or pull request already exists

  
help wanted

Need some help

  
invalid

Something is wrong

  
kind/bug

Something is not working

  
kind/feature

New feature

  
needs reproduction

   
question

More information is needed

  
security

   
wontfix

This won't be fixed

No Label
dependencies
duplicate
help wanted
invalid
kind/bug
kind/feature
needs reproduction
question
security
wontfix
Milestone
Clear milestone
No items
No Milestone
Assignees
Clear assignees
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: vikunja/vikunja#2330
No description provided.
Delete Branch "renovate/dev-dependencies"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?