vikunja
/
vikunja
6
43
Fork 71
Code Issues 150 Pull Requests 15 Packages Releases 32 Activity

chore(deps): update dev-dependencies #2202

Merged
konrad merged 1 commits from renovate/dev-dependencies into main 2024-03-15 07:48:09 +00:00
Conversation 1 Commits 1 Files Changed 4 +133 -147
renovate commented 2024-03-15 00:06:42 +00:00
Member
Copy Link

This PR contains the following updates:

Package Type Update Change
@histoire/plugin-screenshot (source) devDependencies patch 0.17.8 -> 0.17.14
@histoire/plugin-vue (source) devDependencies patch 0.17.13 -> 0.17.14
electron devDependencies patch 29.1.3 -> 29.1.4
esbuild devDependencies patch 0.20.1 -> 0.20.2
happy-dom devDependencies patch 13.8.4 -> 13.8.6
histoire (source) devDependencies patch 0.17.9 -> 0.17.14
vite-plugin-pwa devDependencies patch 0.19.2 -> 0.19.3

Release Notes

Akryum/histoire (@​histoire/plugin-screenshot)

v0.17.14

Compare Source

compare changes

🩹 Fixes
❤️ Contributors
electron/electron (electron)

v29.1.4: electron v29.1.4

Compare Source

Release Notes for v29.1.4

Other Changes

  • Updated Chromium to 122.0.6261.129. #​41583
evanw/esbuild (esbuild)

v0.20.2

Compare Source

  • Support TypeScript experimental decorators on abstract class fields (#​3684)

    With this release, you can now use TypeScript experimental decorators on abstract class fields. This was silently compiled incorrectly in esbuild 0.19.7 and below, and was an error from esbuild 0.19.8 to esbuild 0.20.1. Code such as the following should now work correctly:

    // Original code
const log = (x: any, y: string) => console.log(y)
abstract class Foo { @​log abstract foo: string }
new class extends Foo { foo = '' }

// Old output (with --loader=ts --tsconfig-raw={\"compilerOptions\":{\"experimentalDecorators\":true}})
const log = (x, y) => console.log(y);
class Foo {
}
new class extends Foo {
  foo = "";
}();

// New output (with --loader=ts --tsconfig-raw={\"compilerOptions\":{\"experimentalDecorators\":true}})
const log = (x, y) => console.log(y);
class Foo {
}
__decorateClass([
  log
], Foo.prototype, "foo", 2);
new class extends Foo {
  foo = "";
}();

  • JSON loader now preserves __proto__ properties (#​3700)

    Copying JSON source code into a JavaScript file will change its meaning if a JSON object contains the __proto__ key. A literal __proto__ property in a JavaScript object literal sets the prototype of the object instead of adding a property named __proto__, while a literal __proto__ property in a JSON object literal just adds a property named __proto__. With this release, esbuild will now work around this problem by converting JSON to JavaScript with a computed property key in this case:

    // Original code
import data from 'data:application/json,{"__proto__":{"fail":true}}'
if (Object.getPrototypeOf(data)?.fail) throw 'fail'

// Old output (with --bundle)
(() => {
  // <data:application/json,{"__proto__":{"fail":true}}>
  var json_proto_fail_true_default = { __proto__: { fail: true } };

  // entry.js
  if (Object.getPrototypeOf(json_proto_fail_true_default)?.fail)
    throw "fail";
})();

// New output (with --bundle)
(() => {
  // <data:application/json,{"__proto__":{"fail":true}}>
  var json_proto_fail_true_default = { ["__proto__"]: { fail: true } };

  // example.mjs
  if (Object.getPrototypeOf(json_proto_fail_true_default)?.fail)
    throw "fail";
})();

  • Improve dead code removal of switch statements (#​3659)

    With this release, esbuild will now remove switch statements in branches when minifying if they are known to never be evaluated:

    // Original code
if (true) foo(); else switch (bar) { case 1: baz(); break }

// Old output (with --minify)
if(1)foo();else switch(bar){case 1:}

// New output (with --minify)
foo();

  • Empty enums should behave like an object literal (#​3657)

    TypeScript allows you to create an empty enum and add properties to it at run time. While people usually use an empty object literal for this instead of a TypeScript enum, esbuild's enum transform didn't anticipate this use case and generated undefined instead of {} for an empty enum. With this release, you can now use an empty enum to generate an empty object literal.

    // Original code
enum Foo {}

// Old output (with --loader=ts)
var Foo = /* @&#8203;__PURE__ */ ((Foo2) => {
})(Foo || {});

// New output (with --loader=ts)
var Foo = /* @&#8203;__PURE__ */ ((Foo2) => {
  return Foo2;
})(Foo || {});

  • Handle Yarn Plug'n'Play edge case with tsconfig.json (#​3698)

    Previously a tsconfig.json file that extends another file in a package with an exports map failed to work when Yarn's Plug'n'Play resolution was active. This edge case should work now starting with this release.

  • Work around issues with Deno 1.31+ (#​3682)

    Version 0.20.0 of esbuild changed how the esbuild child process is run in esbuild's API for Deno. Previously it used Deno.run but that API is being removed in favor of Deno.Command. As part of this change, esbuild is now calling the new unref function on esbuild's long-lived child process, which is supposed to allow Deno to exit when your code has finished running even though the child process is still around (previously you had to explicitly call esbuild's stop() function to terminate the child process for Deno to be able to exit).

    However, this introduced a problem for Deno's testing API which now fails some tests that use esbuild with error: Promise resolution is still pending but the event loop has already resolved. It's unclear to me why this is happening. The call to unref was recommended by someone on the Deno core team, and calling Node's equivalent unref API has been working fine for esbuild in Node for a long time. It could be that I'm using it incorrectly, or that there's some reference counting and/or garbage collection bug in Deno's internals, or that Deno's unref just works differently than Node's unref. In any case, it's not good for Deno tests that use esbuild to be failing.

    In this release, I am removing the call to unref to fix this issue. This means that you will now have to call esbuild's stop() function to allow Deno to exit, just like you did before esbuild version 0.20.0 when this regression was introduced.

    Note: This regression wasn't caught earlier because Deno doesn't seem to fail tests that have outstanding setTimeout calls, which esbuild's test harness was using to enforce a maximum test runtime. Adding a setTimeout was allowing esbuild's Deno tests to succeed. So this regression doesn't necessarily apply to all people using tests in Deno.

capricorn86/happy-dom (happy-dom)

v13.8.6

Compare Source

👷‍♂️ Patch fixes

v13.8.5

Compare Source

👷‍♂️ Patch fixes
  • Fixes problem related to invalid pseudo query selectors matching elements (e.g. ":before" should only match the pseudo element and not the actual element) - By @​capricorn86 in task #​1122
  • Adds support for using multiple pseudo query selectors (e.g. ":first-of-type:last-of-type") - By @​capricorn86 in task #​1122
  • Fixes minor typo in HTMLElementConfig - By @​danbentley in task #​1306
vite-pwa/vite-plugin-pwa (vite-plugin-pwa)

v0.19.3

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

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 | |---|---|---|---| | [@histoire/plugin-screenshot](https://github.com/Akryum/histoire) ([source](https://github.com/Akryum/histoire/tree/HEAD/packages/histoire-plugin-screenshot)) | devDependencies | patch | [`0.17.8` -> `0.17.14`](https://renovatebot.com/diffs/npm/@histoire%2fplugin-screenshot/0.17.8/0.17.14) | | [@histoire/plugin-vue](https://github.com/Akryum/histoire) ([source](https://github.com/Akryum/histoire/tree/HEAD/packages/histoire-plugin-vue)) | devDependencies | patch | [`0.17.13` -> `0.17.14`](https://renovatebot.com/diffs/npm/@histoire%2fplugin-vue/0.17.13/0.17.14) | | [electron](https://github.com/electron/electron) | devDependencies | patch | [`29.1.3` -> `29.1.4`](https://renovatebot.com/diffs/npm/electron/29.1.3/29.1.4) | | [esbuild](https://github.com/evanw/esbuild) | devDependencies | patch | [`0.20.1` -> `0.20.2`](https://renovatebot.com/diffs/npm/esbuild/0.20.1/0.20.2) | | [happy-dom](https://github.com/capricorn86/happy-dom) | devDependencies | patch | [`13.8.4` -> `13.8.6`](https://renovatebot.com/diffs/npm/happy-dom/13.8.4/13.8.6) | | [histoire](https://github.com/Akryum/histoire) ([source](https://github.com/Akryum/histoire/tree/HEAD/packages/histoire)) | devDependencies | patch | [`0.17.9` -> `0.17.14`](https://renovatebot.com/diffs/npm/histoire/0.17.9/0.17.14) | | [vite-plugin-pwa](https://github.com/vite-pwa/vite-plugin-pwa) | devDependencies | patch | [`0.19.2` -> `0.19.3`](https://renovatebot.com/diffs/npm/vite-plugin-pwa/0.19.2/0.19.3) | --- ### Release Notes <details> <summary>Akryum/histoire (@&#8203;histoire/plugin-screenshot)</summary> ### [`v0.17.14`](https://github.com/Akryum/histoire/blob/HEAD/CHANGELOG.md#v01714) [Compare Source](https://github.com/Akryum/histoire/compare/v0.17.8...v0.17.14) [compare changes](https://github.com/Akryum/histoire/compare/v0.17.13...v0.17.14) ##### 🩹 Fixes - Force release all packages ([fec0afd3](https://github.com/Akryum/histoire/commit/fec0afd3)) ##### ❤️ Contributors - Guillaume Chau ([@&#8203;Akryum](http://github.com/Akryum)) </details> <details> <summary>electron/electron (electron)</summary> ### [`v29.1.4`](https://github.com/electron/electron/releases/tag/v29.1.4): electron v29.1.4 [Compare Source](https://github.com/electron/electron/compare/v29.1.3...v29.1.4) ### Release Notes for v29.1.4 #### Other Changes - Updated Chromium to 122.0.6261.129. [#&#8203;41583](https://github.com/electron/electron/pull/41583) </details> <details> <summary>evanw/esbuild (esbuild)</summary> ### [`v0.20.2`](https://github.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#0202) [Compare Source](https://github.com/evanw/esbuild/compare/v0.20.1...v0.20.2) - Support TypeScript experimental decorators on `abstract` class fields ([#&#8203;3684](https://github.com/evanw/esbuild/issues/3684)) With this release, you can now use TypeScript experimental decorators on `abstract` class fields. This was silently compiled incorrectly in esbuild 0.19.7 and below, and was an error from esbuild 0.19.8 to esbuild 0.20.1. Code such as the following should now work correctly: ```ts // Original code const log = (x: any, y: string) => console.log(y) abstract class Foo { @&#8203;log abstract foo: string } new class extends Foo { foo = '' } // Old output (with --loader=ts --tsconfig-raw={\"compilerOptions\":{\"experimentalDecorators\":true}}) const log = (x, y) => console.log(y); class Foo { } new class extends Foo { foo = ""; }(); // New output (with --loader=ts --tsconfig-raw={\"compilerOptions\":{\"experimentalDecorators\":true}}) const log = (x, y) => console.log(y); class Foo { } __decorateClass([ log ], Foo.prototype, "foo", 2); new class extends Foo { foo = ""; }(); ``` - JSON loader now preserves `__proto__` properties ([#&#8203;3700](https://github.com/evanw/esbuild/issues/3700)) Copying JSON source code into a JavaScript file will change its meaning if a JSON object contains the `__proto__` key. A literal `__proto__` property in a JavaScript object literal sets the prototype of the object instead of adding a property named `__proto__`, while a literal `__proto__` property in a JSON object literal just adds a property named `__proto__`. With this release, esbuild will now work around this problem by converting JSON to JavaScript with a computed property key in this case: ```js // Original code import data from 'data:application/json,{"__proto__":{"fail":true}}' if (Object.getPrototypeOf(data)?.fail) throw 'fail' // Old output (with --bundle) (() => { // <data:application/json,{"__proto__":{"fail":true}}> var json_proto_fail_true_default = { __proto__: { fail: true } }; // entry.js if (Object.getPrototypeOf(json_proto_fail_true_default)?.fail) throw "fail"; })(); // New output (with --bundle) (() => { // <data:application/json,{"__proto__":{"fail":true}}> var json_proto_fail_true_default = { ["__proto__"]: { fail: true } }; // example.mjs if (Object.getPrototypeOf(json_proto_fail_true_default)?.fail) throw "fail"; })(); ``` - Improve dead code removal of `switch` statements ([#&#8203;3659](https://github.com/evanw/esbuild/issues/3659)) With this release, esbuild will now remove `switch` statements in branches when minifying if they are known to never be evaluated: ```js // Original code if (true) foo(); else switch (bar) { case 1: baz(); break } // Old output (with --minify) if(1)foo();else switch(bar){case 1:} // New output (with --minify) foo(); ``` - Empty enums should behave like an object literal ([#&#8203;3657](https://github.com/evanw/esbuild/issues/3657)) TypeScript allows you to create an empty enum and add properties to it at run time. While people usually use an empty object literal for this instead of a TypeScript enum, esbuild's enum transform didn't anticipate this use case and generated `undefined` instead of `{}` for an empty enum. With this release, you can now use an empty enum to generate an empty object literal. ```ts // Original code enum Foo {} // Old output (with --loader=ts) var Foo = /* @&#8203;__PURE__ */ ((Foo2) => { })(Foo || {}); // New output (with --loader=ts) var Foo = /* @&#8203;__PURE__ */ ((Foo2) => { return Foo2; })(Foo || {}); ``` - Handle Yarn Plug'n'Play edge case with `tsconfig.json` ([#&#8203;3698](https://github.com/evanw/esbuild/issues/3698)) Previously a `tsconfig.json` file that `extends` another file in a package with an `exports` map failed to work when Yarn's Plug'n'Play resolution was active. This edge case should work now starting with this release. - Work around issues with Deno 1.31+ ([#&#8203;3682](https://github.com/evanw/esbuild/issues/3682)) Version 0.20.0 of esbuild changed how the esbuild child process is run in esbuild's API for Deno. Previously it used `Deno.run` but that API is being removed in favor of `Deno.Command`. As part of this change, esbuild is now calling the new `unref` function on esbuild's long-lived child process, which is supposed to allow Deno to exit when your code has finished running even though the child process is still around (previously you had to explicitly call esbuild's `stop()` function to terminate the child process for Deno to be able to exit). However, this introduced a problem for Deno's testing API which now fails some tests that use esbuild with `error: Promise resolution is still pending but the event loop has already resolved`. It's unclear to me why this is happening. The call to `unref` was recommended by someone on the Deno core team, and calling Node's equivalent `unref` API has been working fine for esbuild in Node for a long time. It could be that I'm using it incorrectly, or that there's some reference counting and/or garbage collection bug in Deno's internals, or that Deno's `unref` just works differently than Node's `unref`. In any case, it's not good for Deno tests that use esbuild to be failing. In this release, I am removing the call to `unref` to fix this issue. This means that you will now have to call esbuild's `stop()` function to allow Deno to exit, just like you did before esbuild version 0.20.0 when this regression was introduced. Note: This regression wasn't caught earlier because Deno doesn't seem to fail tests that have outstanding `setTimeout` calls, which esbuild's test harness was using to enforce a maximum test runtime. Adding a `setTimeout` was allowing esbuild's Deno tests to succeed. So this regression doesn't necessarily apply to all people using tests in Deno. </details> <details> <summary>capricorn86/happy-dom (happy-dom)</summary> ### [`v13.8.6`](https://github.com/capricorn86/happy-dom/releases/tag/v13.8.6) [Compare Source](https://github.com/capricorn86/happy-dom/compare/v13.8.5...v13.8.6) ##### :construction_worker_man: Patch fixes - Fixes bug related to multiple fallbacks to CSS variables being set incorrectly - By **[@&#8203;odanado](https://github.com/odanado)** and **[@&#8203;capricorn86](https://github.com/capricorn86)** in task [#&#8203;1308](https://github.com/capricorn86/happy-dom/issues/1308) ### [`v13.8.5`](https://github.com/capricorn86/happy-dom/releases/tag/v13.8.5) [Compare Source](https://github.com/capricorn86/happy-dom/compare/v13.8.4...v13.8.5) ##### :construction_worker_man: Patch fixes - Fixes problem related to invalid pseudo query selectors matching elements (e.g. ":before" should only match the pseudo element and not the actual element) - By **[@&#8203;capricorn86](https://github.com/capricorn86)** in task [#&#8203;1122](https://github.com/capricorn86/happy-dom/issues/1122) - Adds support for using multiple pseudo query selectors (e.g. ":first-of-type:last-of-type") - By **[@&#8203;capricorn86](https://github.com/capricorn86)** in task [#&#8203;1122](https://github.com/capricorn86/happy-dom/issues/1122) - Fixes minor typo in `HTMLElementConfig` - By **[@&#8203;danbentley](https://github.com/danbentley)** in task [#&#8203;1306](https://github.com/capricorn86/happy-dom/issues/1306) </details> <details> <summary>vite-pwa/vite-plugin-pwa (vite-plugin-pwa)</summary> ### [`v0.19.3`](https://github.com/vite-pwa/vite-plugin-pwa/releases/tag/v0.19.3) [Compare Source](https://github.com/vite-pwa/vite-plugin-pwa/compare/v0.19.2...v0.19.3) #####    🐞 Bug Fixes - Pwa assets disabled when using inlined configuration  -  by [@&#8203;userquin](https://github.com/userquin) in https://github.com/vite-pwa/vite-plugin-pwa/issues/685 [<samp>(7ffeb)</samp>](https://github.com/vite-pwa/vite-plugin-pwa/commit/7ffeb44) #####     [View changes on GitHub](https://github.com/vite-pwa/vite-plugin-pwa/compare/v0.19.2...v0.19.3) </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:eyJjcmVhdGVkSW5WZXIiOiIzNy4xNzUuMCIsInVwZGF0ZWRJblZlciI6IjM3LjE3NS4wIiwidGFyZ2V0QnJhbmNoIjoibWFpbiJ9-->
renovate added the
dependencies
 label 2024-03-15 00:06:42 +00:00
renovate added 1 commit 2024-03-15 00:06:43 +00:00
continuous-integration/drone/pr Build is passing Details
continuous-integration/drone/push Build is failing Details
2add517d6e chore(deps): update dev-dependencies
frederick commented 2024-03-15 00:23:25 +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://2202-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://2202-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.
konrad merged commit 2add517d6e into main 2024-03-15 07:48:09 +00:00
konrad deleted branch renovate/dev-dependencies 2024-03-15 07:48:09 +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#2202
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?