vikunja
/
frontend
Archived
6
39
Fork 49
Code Issues 1 Pull Requests 4 Projects Releases 26 Activity

chore(deps): update dev-dependencies #3746

Merged
konrad merged 2 commits from renovate/dev-dependencies into main 2023-09-15 11:59:32 +00:00
Conversation 2 Commits 2 Files Changed 2 +289 -308
renovate commented 2023-09-14 00:10:01 +00:00
Member
Copy Link

This PR contains the following updates:

Package Type Update Change
@4tw/cypress-drag-drop devDependencies patch 2.2.4 -> 2.2.5
@rushstack/eslint-patch (source) devDependencies minor 1.3.3 -> 1.4.0
@tsconfig/node18 devDependencies patch 18.2.1 -> 18.2.2
@types/flexsearch (source) devDependencies patch 0.7.3 -> 0.7.4
@types/node (source) devDependencies patch 18.17.14 -> 18.17.16
@typescript-eslint/eslint-plugin devDependencies minor 6.6.0 -> 6.7.0
@typescript-eslint/parser devDependencies minor 6.6.0 -> 6.7.0
caniuse-lite devDependencies patch 1.0.30001528 -> 1.0.30001534
esbuild devDependencies patch 0.19.2 -> 0.19.3
eslint (source) devDependencies minor 8.48.0 -> 8.49.0
rollup (source) devDependencies patch 3.29.0 -> 3.29.1
sass devDependencies minor 1.66.1 -> 1.67.0
vite-plugin-pwa devDependencies patch 0.16.4 -> 0.16.5
vitest devDependencies patch 0.34.3 -> 0.34.4
vue-tsc devDependencies patch 1.8.10 -> 1.8.11

Release Notes

4teamwork/cypress-drag-drop (@​4tw/cypress-drag-drop)

v2.2.5

Compare Source

  • Add support for Cypress 13.x.
tsconfig/bases (@​tsconfig/node18)

v18.2.2

Compare Source

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

v6.7.0

Compare Source

Bug Fixes
  • eslint-plugin: [no-restricted-imports] disallow side effect imports when allowTypeImports is enabled (#​7560) (4908905)
Features
  • eslint-plugin: [await-thenable] added suggestion fixer (#​7437) (b284370)

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

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

v6.7.0

Compare Source

Note: Version bump only for package @​typescript-eslint/parser

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

browserslist/caniuse-lite (caniuse-lite)

v1.0.30001534

Compare Source

v1.0.30001533

Compare Source

v1.0.30001532

Compare Source

v1.0.30001529

Compare Source

evanw/esbuild (esbuild)

v0.19.3

Compare Source

  • Fix list-style-type with the local-css loader (#​3325)

    The local-css loader incorrectly treated all identifiers provided to list-style-type as a custom local identifier. That included identifiers such as none which have special meaning in CSS, and which should not be treated as custom local identifiers. This release fixes this bug:

    /* Original code */
ul { list-style-type: none }

/* Old output (with --loader=local-css) */
ul {
  list-style-type: stdin_none;
}

/* New output (with --loader=local-css) */
ul {
  list-style-type: none;
}

    Note that this bug only affected code using the local-css loader. It did not affect code using the css loader.

  • Avoid inserting temporary variables before use strict (#​3322)

    This release fixes a bug where esbuild could incorrectly insert automatically-generated temporary variables before use strict directives:

    // Original code
function foo() {
  'use strict'
  a.b?.c()
}

// Old output (with --target=es6)
function foo() {
  var _a;
  "use strict";
  (_a = a.b) == null ? void 0 : _a.c();
}

// New output (with --target=es6)
function foo() {
  "use strict";
  var _a;
  (_a = a.b) == null ? void 0 : _a.c();
}

  • Adjust TypeScript enum output to better approximate tsc (#​3329)

    TypeScript enum values can be either number literals or string literals. Numbers create a bidirectional mapping between the name and the value but strings only create a unidirectional mapping from the name to the value. When the enum value is neither a number literal nor a string literal, TypeScript and esbuild both default to treating it as a number:

    // Original TypeScript code
declare const foo: any
enum Foo {
  NUMBER = 1,
  STRING = 'a',
  OTHER = foo,
}

// Compiled JavaScript code (from "tsc")
var Foo;
(function (Foo) {
  Foo[Foo["NUMBER"] = 1] = "NUMBER";
  Foo["STRING"] = "a";
  Foo[Foo["OTHER"] = foo] = "OTHER";
})(Foo || (Foo = {}));

    However, TypeScript does constant folding slightly differently than esbuild. For example, it may consider template literals to be string literals in some cases:

    // Original TypeScript code
declare const foo = 'foo'
enum Foo {
  PRESENT = `${foo}`,
  MISSING = `${bar}`,
}

// Compiled JavaScript code (from "tsc")
var Foo;
(function (Foo) {
  Foo["PRESENT"] = "foo";
  Foo[Foo["MISSING"] = `${bar}`] = "MISSING";
})(Foo || (Foo = {}));

    The template literal initializer for PRESENT is treated as a string while the template literal initializer for MISSING is treated as a number. Previously esbuild treated both of these cases as a number but starting with this release, esbuild will now treat both of these cases as a string. This doesn't exactly match the behavior of tsc but in the case where the behavior diverges tsc reports a compile error, so this seems like acceptible behavior for esbuild. Note that handling these cases completely correctly would require esbuild to parse type declarations (see the declare keyword), which esbuild deliberately doesn't do.

  • Ignore case in CSS in more places (#​3316)

    This release makes esbuild's CSS support more case-agnostic, which better matches how browsers work. For example:

    /* Original code */
@​KeyFrames Foo { From { OpaCity: 0 } To { OpaCity: 1 } }
body { CoLoR: YeLLoW }

/* Old output (with --minify) */
@​KeyFrames Foo{From {OpaCity: 0} To {OpaCity: 1}}body{CoLoR:YeLLoW}

/* New output (with --minify) */
@​KeyFrames Foo{0%{OpaCity:0}To{OpaCity:1}}body{CoLoR:#ff0}

    Please never actually write code like this.

  • Improve the error message for null entries in exports (#​3377)

    Package authors can disable package export paths with the exports map in package.json. With this release, esbuild now has a clearer error message that points to the null token in package.json itself instead of to the surrounding context. Here is an example of the new error message:

    ✘ [ERROR] Could not resolve "msw/browser"

    lib/msw-config.ts:2:28:
      2 │ import { setupWorker } from 'msw/browser';
        ╵                             ~~~~~~~~~~~~~

  The path "./browser" cannot be imported from package "msw" because it was explicitly disabled by
  the package author here:

    node_modules/msw/package.json:17:14:
      17 │       "node": null,
         ╵               ~~~~

  You can mark the path "msw/browser" as external to exclude it from the bundle, which will remove
  this error and leave the unresolved path in the bundle.

  • Parse and print the with keyword in import statements

    JavaScript was going to have a feature called "import assertions" that adds an assert keyword to import statements. It looked like this:

    import stuff from './stuff.json' assert { type: 'json' }

    The feature provided a way to assert that the imported file is of a certain type (but was not allowed to affect how the import is interpreted, even though that's how everyone expected it to behave). The feature was fully specified and then actually implemented and shipped in Chrome before the people behind the feature realized that they should allow it to affect how the import is interpreted after all. So import assertions are no longer going to be added to the language.

    Instead, the current proposal is to add a feature called "import attributes" instead that adds a with keyword to import statements. It looks like this:

    import stuff from './stuff.json' with { type: 'json' }

    This feature provides a way to affect how the import is interpreted. With this release, esbuild now has preliminary support for parsing and printing this new with keyword. The with keyword is not yet interpreted by esbuild, however, so bundling code with it will generate a build error. All this release does is allow you to use esbuild to process code containing it (such as removing types from TypeScript code). Note that this syntax is not yet a part of JavaScript and may be removed or altered in the future if the specification changes (which it already has once, as described above). If that happens, esbuild reserves the right to remove or alter its support for this syntax too.

eslint/eslint (eslint)

v8.49.0

Compare Source

Features

  • da09f4e feat: Implement onUnreachableCodePathStart/End (#​17511) (Nicholas C. Zakas)
  • 32b2327 feat: Emit deprecation warnings in RuleTester (#​17527) (Nicholas C. Zakas)
  • acb7df3 feat: add new enforce option to lines-between-class-members (#​17462) (Nitin Kumar)

Documentation

  • ecfb54f docs: Update README (GitHub Actions Bot)
  • de86b3b docs: update no-promise-executor-return examples (#​17529) (Nitin Kumar)
  • 032c4b1 docs: add typescript template (#​17500) (James)
  • cd7da5c docs: Update README (GitHub Actions Bot)

Chores

rollup/rollup (rollup)

v3.29.1

Compare Source

2023-09-10

Bug Fixes
  • Fix time measurement of plugin hooks in watch mode (#​5114)
  • Ensure accessing document.currentScript in import.meta.url returns correct results (#​5118)
Pull Requests
sass/dart-sass (sass)

v1.67.0

Compare Source

  • All functions defined in CSS Values and Units 4 are now once again parsed as
    calculation objects: round(), mod(), rem(), sin(), cos(), tan(),
    asin(), acos(), atan(), atan2(), pow(), sqrt(), hypot(),
    log(), exp(), abs(), and sign().

    Unlike in 1.65.0, function calls are not locked into being parsed as
    calculations or plain Sass functions at parse-time. This means that
    user-defined functions will take precedence over CSS calculations of the same
    name. Although the function names calc() and clamp() are still forbidden,
    users may continue to freely define functions whose names overlap with other
    CSS calculations (including abs(), min(), max(), and round() whose
    names overlap with global Sass functions).

  • As a consequence of the change in calculation parsing described above,
    calculation functions containing interpolation are now parsed more strictly
    than before. However, all interpolations that would have produced valid CSS
    will continue to work, so this is not considered a breaking change.

  • Interpolations in calculation functions that aren't used in a position that
    could also have a normal calculation value are now deprecated. For example,
    calc(1px #{"+ 2px"}) is deprecated, but calc(1px + #{"2px"}) is still
    allowed. This deprecation is named calc-interp. See the Sass website for
    more information.

  • Potentially breaking bug fix: The importer used to load a given file is no
    longer used to load absolute URLs that appear in that file. This was
    unintented behavior that contradicted the Sass specification. Absolute URLs
    will now correctly be loaded only from the global importer list. This applies
    to the modern JS API, the Dart API, and the embedded protocol.

Embedded Sass
  • Substantially improve the embedded compiler's performance when compiling many
    files or files that require many importer or function call round-trips with
    the embedded host.
antfu/vite-plugin-pwa (vite-plugin-pwa)

v0.16.5

Compare Source

   🚀 Features
    View changes on GitHub
vitest-dev/vitest (vitest)

v0.34.4

Compare Source

   🐞 Bug Fixes
    View changes on GitHub
vuejs/language-tools (vue-tsc)

v1.8.11

Compare Source

  • feat: slot references codeLens counting fragment default slot (#​932)
  • fix: correct message for @vue-expect-error (#​3541) - thanks @​so1ve
  • fix: avoid global macros conflicts with local variables (#​3550) - thanks @​so1ve
  • fix: script setup comments at top breaks global macros (#​3549) - thanks @​so1ve
  • fix(vue-tsc): prevent rebuild in incremental mode throwing error (#​3556) - thanks @​blake-newman
Full-time Support by

WebContainer API is here.
Our Platinum Sponsors
The Intuitive Web Framework
The Progressive JavaScript Framework
Our Silver Sponsors
Add you via GitHub Sponsors or Open Collective

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 | |---|---|---|---| | [@4tw/cypress-drag-drop](https://github.com/4teamwork/cypress-drag-drop) | devDependencies | patch | [`2.2.4` -> `2.2.5`](https://renovatebot.com/diffs/npm/@4tw%2fcypress-drag-drop/2.2.4/2.2.5) | | [@rushstack/eslint-patch](https://rushstack.io) ([source](https://github.com/microsoft/rushstack)) | devDependencies | minor | [`1.3.3` -> `1.4.0`](https://renovatebot.com/diffs/npm/@rushstack%2feslint-patch/1.3.3/1.4.0) | | [@tsconfig/node18](https://github.com/tsconfig/bases) | devDependencies | patch | [`18.2.1` -> `18.2.2`](https://renovatebot.com/diffs/npm/@tsconfig%2fnode18/18.2.1/18.2.2) | | [@types/flexsearch](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/flexsearch) ([source](https://github.com/DefinitelyTyped/DefinitelyTyped)) | devDependencies | patch | [`0.7.3` -> `0.7.4`](https://renovatebot.com/diffs/npm/@types%2fflexsearch/0.7.3/0.7.4) | | [@types/node](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/node) ([source](https://github.com/DefinitelyTyped/DefinitelyTyped)) | devDependencies | patch | [`18.17.14` -> `18.17.16`](https://renovatebot.com/diffs/npm/@types%2fnode/18.17.14/18.17.16) | | [@typescript-eslint/eslint-plugin](https://github.com/typescript-eslint/typescript-eslint) | devDependencies | minor | [`6.6.0` -> `6.7.0`](https://renovatebot.com/diffs/npm/@typescript-eslint%2feslint-plugin/6.6.0/6.7.0) | | [@typescript-eslint/parser](https://github.com/typescript-eslint/typescript-eslint) | devDependencies | minor | [`6.6.0` -> `6.7.0`](https://renovatebot.com/diffs/npm/@typescript-eslint%2fparser/6.6.0/6.7.0) | | [caniuse-lite](https://github.com/browserslist/caniuse-lite) | devDependencies | patch | [`1.0.30001528` -> `1.0.30001534`](https://renovatebot.com/diffs/npm/caniuse-lite/1.0.30001528/1.0.30001534) | | [esbuild](https://github.com/evanw/esbuild) | devDependencies | patch | [`0.19.2` -> `0.19.3`](https://renovatebot.com/diffs/npm/esbuild/0.19.2/0.19.3) | | [eslint](https://eslint.org) ([source](https://github.com/eslint/eslint)) | devDependencies | minor | [`8.48.0` -> `8.49.0`](https://renovatebot.com/diffs/npm/eslint/8.48.0/8.49.0) | | [rollup](https://rollupjs.org/) ([source](https://github.com/rollup/rollup)) | devDependencies | patch | [`3.29.0` -> `3.29.1`](https://renovatebot.com/diffs/npm/rollup/3.29.0/3.29.1) | | [sass](https://github.com/sass/dart-sass) | devDependencies | minor | [`1.66.1` -> `1.67.0`](https://renovatebot.com/diffs/npm/sass/1.66.1/1.67.0) | | [vite-plugin-pwa](https://github.com/antfu/vite-plugin-pwa) | devDependencies | patch | [`0.16.4` -> `0.16.5`](https://renovatebot.com/diffs/npm/vite-plugin-pwa/0.16.4/0.16.5) | | [vitest](https://github.com/vitest-dev/vitest) | devDependencies | patch | [`0.34.3` -> `0.34.4`](https://renovatebot.com/diffs/npm/vitest/0.34.3/0.34.4) | | [vue-tsc](https://github.com/vuejs/language-tools) | devDependencies | patch | [`1.8.10` -> `1.8.11`](https://renovatebot.com/diffs/npm/vue-tsc/1.8.10/1.8.11) | --- ### Release Notes <details> <summary>4teamwork/cypress-drag-drop (@&#8203;4tw/cypress-drag-drop)</summary> ### [`v2.2.5`](https://github.com/4teamwork/cypress-drag-drop/blob/HEAD/CHANGELOG.md#225---2023-09-14) [Compare Source](https://github.com/4teamwork/cypress-drag-drop/compare/v2.2.4...v2.2.5) - Add support for Cypress 13.x. </details> <details> <summary>tsconfig/bases (@&#8203;tsconfig/node18)</summary> ### [`v18.2.2`](https://github.com/tsconfig/bases/compare/5ee68ffc8325546335649525a3553067d2d27830...031273b815ff7f672c7c9057fb7d19ef363054b1) [Compare Source](https://github.com/tsconfig/bases/compare/5ee68ffc8325546335649525a3553067d2d27830...031273b815ff7f672c7c9057fb7d19ef363054b1) </details> <details> <summary>typescript-eslint/typescript-eslint (@&#8203;typescript-eslint/eslint-plugin)</summary> ### [`v6.7.0`](https://github.com/typescript-eslint/typescript-eslint/blob/HEAD/packages/eslint-plugin/CHANGELOG.md#670-2023-09-11) [Compare Source](https://github.com/typescript-eslint/typescript-eslint/compare/v6.6.0...v6.7.0) ##### Bug Fixes - **eslint-plugin:** \[no-restricted-imports] disallow side effect imports when allowTypeImports is enabled ([#&#8203;7560](https://github.com/typescript-eslint/typescript-eslint/issues/7560)) ([4908905](https://github.com/typescript-eslint/typescript-eslint/commit/4908905e4ee2b533504fcba0c671aa869668df25)) ##### Features - **eslint-plugin:** \[await-thenable] added suggestion fixer ([#&#8203;7437](https://github.com/typescript-eslint/typescript-eslint/issues/7437)) ([b284370](https://github.com/typescript-eslint/typescript-eslint/commit/b284370e1e95493764d2806cd45975201e02f374)) You can read about our [versioning strategy](https://main--typescript-eslint.netlify.app/users/versioning) and [releases](https://main--typescript-eslint.netlify.app/users/releases) on our website. </details> <details> <summary>typescript-eslint/typescript-eslint (@&#8203;typescript-eslint/parser)</summary> ### [`v6.7.0`](https://github.com/typescript-eslint/typescript-eslint/blob/HEAD/packages/parser/CHANGELOG.md#670-2023-09-11) [Compare Source](https://github.com/typescript-eslint/typescript-eslint/compare/v6.6.0...v6.7.0) **Note:** Version bump only for package [@&#8203;typescript-eslint/parser](https://github.com/typescript-eslint/parser) You can read about our [versioning strategy](https://main--typescript-eslint.netlify.app/users/versioning) and [releases](https://main--typescript-eslint.netlify.app/users/releases) on our website. </details> <details> <summary>browserslist/caniuse-lite (caniuse-lite)</summary> ### [`v1.0.30001534`](https://github.com/browserslist/caniuse-lite/compare/1.0.30001533...1.0.30001534) [Compare Source](https://github.com/browserslist/caniuse-lite/compare/1.0.30001533...1.0.30001534) ### [`v1.0.30001533`](https://github.com/browserslist/caniuse-lite/compare/1.0.30001532...1.0.30001533) [Compare Source](https://github.com/browserslist/caniuse-lite/compare/1.0.30001532...1.0.30001533) ### [`v1.0.30001532`](https://github.com/browserslist/caniuse-lite/compare/1.0.30001529...1.0.30001532) [Compare Source](https://github.com/browserslist/caniuse-lite/compare/1.0.30001529...1.0.30001532) ### [`v1.0.30001529`](https://github.com/browserslist/caniuse-lite/compare/1.0.30001528...1.0.30001529) [Compare Source](https://github.com/browserslist/caniuse-lite/compare/1.0.30001528...1.0.30001529) </details> <details> <summary>evanw/esbuild (esbuild)</summary> ### [`v0.19.3`](https://github.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#0193) [Compare Source](https://github.com/evanw/esbuild/compare/v0.19.2...v0.19.3) - Fix `list-style-type` with the `local-css` loader ([#&#8203;3325](https://github.com/evanw/esbuild/issues/3325)) The `local-css` loader incorrectly treated all identifiers provided to `list-style-type` as a custom local identifier. That included identifiers such as `none` which have special meaning in CSS, and which should not be treated as custom local identifiers. This release fixes this bug: ```css /* Original code */ ul { list-style-type: none } /* Old output (with --loader=local-css) */ ul { list-style-type: stdin_none; } /* New output (with --loader=local-css) */ ul { list-style-type: none; } ``` Note that this bug only affected code using the `local-css` loader. It did not affect code using the `css` loader. - Avoid inserting temporary variables before `use strict` ([#&#8203;3322](https://github.com/evanw/esbuild/issues/3322)) This release fixes a bug where esbuild could incorrectly insert automatically-generated temporary variables before `use strict` directives: ```js // Original code function foo() { 'use strict' a.b?.c() } // Old output (with --target=es6) function foo() { var _a; "use strict"; (_a = a.b) == null ? void 0 : _a.c(); } // New output (with --target=es6) function foo() { "use strict"; var _a; (_a = a.b) == null ? void 0 : _a.c(); } ``` - Adjust TypeScript `enum` output to better approximate `tsc` ([#&#8203;3329](https://github.com/evanw/esbuild/issues/3329)) TypeScript enum values can be either number literals or string literals. Numbers create a bidirectional mapping between the name and the value but strings only create a unidirectional mapping from the name to the value. When the enum value is neither a number literal nor a string literal, TypeScript and esbuild both default to treating it as a number: ```ts // Original TypeScript code declare const foo: any enum Foo { NUMBER = 1, STRING = 'a', OTHER = foo, } // Compiled JavaScript code (from "tsc") var Foo; (function (Foo) { Foo[Foo["NUMBER"] = 1] = "NUMBER"; Foo["STRING"] = "a"; Foo[Foo["OTHER"] = foo] = "OTHER"; })(Foo || (Foo = {})); ``` However, TypeScript does constant folding slightly differently than esbuild. For example, it may consider template literals to be string literals in some cases: ```ts // Original TypeScript code declare const foo = 'foo' enum Foo { PRESENT = `${foo}`, MISSING = `${bar}`, } // Compiled JavaScript code (from "tsc") var Foo; (function (Foo) { Foo["PRESENT"] = "foo"; Foo[Foo["MISSING"] = `${bar}`] = "MISSING"; })(Foo || (Foo = {})); ``` The template literal initializer for `PRESENT` is treated as a string while the template literal initializer for `MISSING` is treated as a number. Previously esbuild treated both of these cases as a number but starting with this release, esbuild will now treat both of these cases as a string. This doesn't exactly match the behavior of `tsc` but in the case where the behavior diverges `tsc` reports a compile error, so this seems like acceptible behavior for esbuild. Note that handling these cases completely correctly would require esbuild to parse type declarations (see the `declare` keyword), which esbuild deliberately doesn't do. - Ignore case in CSS in more places ([#&#8203;3316](https://github.com/evanw/esbuild/issues/3316)) This release makes esbuild's CSS support more case-agnostic, which better matches how browsers work. For example: ```css /* Original code */ @&#8203;KeyFrames Foo { From { OpaCity: 0 } To { OpaCity: 1 } } body { CoLoR: YeLLoW } /* Old output (with --minify) */ @&#8203;KeyFrames Foo{From {OpaCity: 0} To {OpaCity: 1}}body{CoLoR:YeLLoW} /* New output (with --minify) */ @&#8203;KeyFrames Foo{0%{OpaCity:0}To{OpaCity:1}}body{CoLoR:#ff0} ``` Please never actually write code like this. - Improve the error message for `null` entries in `exports` ([#&#8203;3377](https://github.com/evanw/esbuild/issues/3377)) Package authors can disable package export paths with the `exports` map in `package.json`. With this release, esbuild now has a clearer error message that points to the `null` token in `package.json` itself instead of to the surrounding context. Here is an example of the new error message: ✘ [ERROR] Could not resolve "msw/browser" lib/msw-config.ts:2:28: 2 │ import { setupWorker } from 'msw/browser'; ╵ ~~~~~~~~~~~~~ The path "./browser" cannot be imported from package "msw" because it was explicitly disabled by the package author here: node_modules/msw/package.json:17:14: 17 │ "node": null, ╵ ~~~~ You can mark the path "msw/browser" as external to exclude it from the bundle, which will remove this error and leave the unresolved path in the bundle. - Parse and print the `with` keyword in `import` statements JavaScript was going to have a feature called "import assertions" that adds an `assert` keyword to `import` statements. It looked like this: ```js import stuff from './stuff.json' assert { type: 'json' } ``` The feature provided a way to assert that the imported file is of a certain type (but was not allowed to affect how the import is interpreted, even though that's how everyone expected it to behave). The feature was fully specified and then actually implemented and shipped in Chrome before the people behind the feature realized that they should allow it to affect how the import is interpreted after all. So import assertions are no longer going to be added to the language. Instead, the [current proposal](https://github.com/tc39/proposal-import-attributes) is to add a feature called "import attributes" instead that adds a `with` keyword to import statements. It looks like this: ```js import stuff from './stuff.json' with { type: 'json' } ``` This feature provides a way to affect how the import is interpreted. With this release, esbuild now has preliminary support for parsing and printing this new `with` keyword. The `with` keyword is not yet interpreted by esbuild, however, so bundling code with it will generate a build error. All this release does is allow you to use esbuild to process code containing it (such as removing types from TypeScript code). Note that this syntax is not yet a part of JavaScript and may be removed or altered in the future if the specification changes (which it already has once, as described above). If that happens, esbuild reserves the right to remove or alter its support for this syntax too. </details> <details> <summary>eslint/eslint (eslint)</summary> ### [`v8.49.0`](https://github.com/eslint/eslint/releases/tag/v8.49.0) [Compare Source](https://github.com/eslint/eslint/compare/v8.48.0...v8.49.0) #### Features - [`da09f4e`](https://github.com/eslint/eslint/commit/da09f4e641141f585ef611c6e9d63d4331054706) feat: Implement onUnreachableCodePathStart/End ([#&#8203;17511](https://github.com/eslint/eslint/issues/17511)) (Nicholas C. Zakas) - [`32b2327`](https://github.com/eslint/eslint/commit/32b2327aafdd3b911fabab69ed75c9ff97658c60) feat: Emit deprecation warnings in RuleTester ([#&#8203;17527](https://github.com/eslint/eslint/issues/17527)) (Nicholas C. Zakas) - [`acb7df3`](https://github.com/eslint/eslint/commit/acb7df35b9a7485f26bc6b3e1f9083d1c585dce9) feat: add new `enforce` option to `lines-between-class-members` ([#&#8203;17462](https://github.com/eslint/eslint/issues/17462)) (Nitin Kumar) #### Documentation - [`ecfb54f`](https://github.com/eslint/eslint/commit/ecfb54ff4cdd18f28b4f9b78f0a78fb4cf80f1b8) docs: Update README (GitHub Actions Bot) - [`de86b3b`](https://github.com/eslint/eslint/commit/de86b3b2e58edd5826200c23255d8325abe375e1) docs: update `no-promise-executor-return` examples ([#&#8203;17529](https://github.com/eslint/eslint/issues/17529)) (Nitin Kumar) - [`032c4b1`](https://github.com/eslint/eslint/commit/032c4b1476a7b8cfd917a66772d2221950ea87eb) docs: add typescript template ([#&#8203;17500](https://github.com/eslint/eslint/issues/17500)) (James) - [`cd7da5c`](https://github.com/eslint/eslint/commit/cd7da5cc3154f86f7ca45fb58929d27a7af359ed) docs: Update README (GitHub Actions Bot) #### Chores - [`b7621c3`](https://github.com/eslint/eslint/commit/b7621c3b16cf7d5539f05336a827e1b32d95e6ac) chore: remove browser test from `npm test` ([#&#8203;17550](https://github.com/eslint/eslint/issues/17550)) (Milos Djermanovic) - [`cac45d0`](https://github.com/eslint/eslint/commit/cac45d04b890b0700dd8908927300608adad05fe) chore: upgrade [@&#8203;eslint/js](https://github.com/eslint/js)[@&#8203;8](https://github.com/8).49.0 ([#&#8203;17549](https://github.com/eslint/eslint/issues/17549)) (Milos Djermanovic) - [`cd39508`](https://github.com/eslint/eslint/commit/cd395082bffcb4b68efa09226d7c682cef56179e) chore: package.json update for [@&#8203;eslint/js](https://github.com/eslint/js) release (ESLint Jenkins) - [`203a971`](https://github.com/eslint/eslint/commit/203a971c0abc3a95ae02ff74104a01e569707060) ci: bump actions/checkout from 3 to 4 ([#&#8203;17530](https://github.com/eslint/eslint/issues/17530)) (dependabot\[bot]) - [`a40fa50`](https://github.com/eslint/eslint/commit/a40fa509922b36bb986eb1be9394591f84f62d9e) chore: use eslint-plugin-jsdoc's flat config ([#&#8203;17516](https://github.com/eslint/eslint/issues/17516)) (Milos Djermanovic) - [`926a286`](https://github.com/eslint/eslint/commit/926a28684282aeec37680bbc52a66973b8055f54) test: replace Karma with Webdriver.IO ([#&#8203;17126](https://github.com/eslint/eslint/issues/17126)) (Christian Bromann) - [`f591d2c`](https://github.com/eslint/eslint/commit/f591d2c88bf15af72e3a207b34fa872b4b90464b) chore: Upgrade config-array ([#&#8203;17512](https://github.com/eslint/eslint/issues/17512)) (Nicholas C. Zakas) </details> <details> <summary>rollup/rollup (rollup)</summary> ### [`v3.29.1`](https://github.com/rollup/rollup/blob/HEAD/CHANGELOG.md#3291) [Compare Source](https://github.com/rollup/rollup/compare/v3.29.0...v3.29.1) *2023-09-10* ##### Bug Fixes - Fix time measurement of plugin hooks in watch mode ([#&#8203;5114](https://github.com/rollup/rollup/issues/5114)) - Ensure accessing document.currentScript in import.meta.url returns correct results ([#&#8203;5118](https://github.com/rollup/rollup/issues/5118)) ##### Pull Requests - [#&#8203;5114](https://github.com/rollup/rollup/pull/5114): fix(perf): avoid superfluous timer wrappings in watch mode ([@&#8203;ZhengLiu2825](https://github.com/ZhengLiu2825)) - [#&#8203;5118](https://github.com/rollup/rollup/pull/5118): fix: access document.currentScript at the top level ([@&#8203;TrickyPi](https://github.com/TrickyPi)) - [#&#8203;5125](https://github.com/rollup/rollup/pull/5125): chore(deps): update actions/checkout action to v4 ([@&#8203;renovate](https://github.com/renovate)\[bot]) - [#&#8203;5126](https://github.com/rollup/rollup/pull/5126): chore(deps): lock file maintenance minor/patch updates ([@&#8203;renovate](https://github.com/renovate)\[bot]) - [#&#8203;5129](https://github.com/rollup/rollup/pull/5129): re-enbale repl-artefacts workflow for rollup-swc branch ([@&#8203;TrickyPi](https://github.com/TrickyPi)) </details> <details> <summary>sass/dart-sass (sass)</summary> ### [`v1.67.0`](https://github.com/sass/dart-sass/blob/HEAD/CHANGELOG.md#1670) [Compare Source](https://github.com/sass/dart-sass/compare/1.66.1...1.67.0) - All functions defined in CSS Values and Units 4 are now once again parsed as calculation objects: `round()`, `mod()`, `rem()`, `sin()`, `cos()`, `tan()`, `asin()`, `acos()`, `atan()`, `atan2()`, `pow()`, `sqrt()`, `hypot()`, `log()`, `exp()`, `abs()`, and `sign()`. Unlike in 1.65.0, function calls are *not* locked into being parsed as calculations or plain Sass functions at parse-time. This means that user-defined functions will take precedence over CSS calculations of the same name. Although the function names `calc()` and `clamp()` are still forbidden, users may continue to freely define functions whose names overlap with other CSS calculations (including `abs()`, `min()`, `max()`, and `round()` whose names overlap with global Sass functions). - As a consequence of the change in calculation parsing described above, calculation functions containing interpolation are now parsed more strictly than before. However, all interpolations that would have produced valid CSS will continue to work, so this is not considered a breaking change. - Interpolations in calculation functions that aren't used in a position that could also have a normal calculation value are now deprecated. For example, `calc(1px #{"+ 2px"})` is deprecated, but `calc(1px + #{"2px"})` is still allowed. This deprecation is named `calc-interp`. See [the Sass website] for more information. [the Sass website]: https://sass-lang.com/d/calc-interp - **Potentially breaking bug fix**: The importer used to load a given file is no longer used to load absolute URLs that appear in that file. This was unintented behavior that contradicted the Sass specification. Absolute URLs will now correctly be loaded only from the global importer list. This applies to the modern JS API, the Dart API, and the embedded protocol. ##### Embedded Sass - Substantially improve the embedded compiler's performance when compiling many files or files that require many importer or function call round-trips with the embedded host. </details> <details> <summary>antfu/vite-plugin-pwa (vite-plugin-pwa)</summary> ### [`v0.16.5`](https://github.com/vite-pwa/vite-plugin-pwa/releases/tag/v0.16.5) [Compare Source](https://github.com/antfu/vite-plugin-pwa/compare/v0.16.4...v0.16.5) #####    🚀 Features - Add `scope_extensions` to webmanifest  -  by [@&#8203;dargmuesli](https://github.com/dargmuesli) in https://github.com/vite-pwa/vite-plugin-pwa/issues/561 [<samp>(81ad4)</samp>](https://github.com/vite-pwa/vite-plugin-pwa/commit/81ad480) - Add `screenshots.form_factor` to webmanifest  -  by [@&#8203;dargmuesli](https://github.com/dargmuesli) in https://github.com/vite-pwa/vite-plugin-pwa/issues/562 [<samp>(92f79)</samp>](https://github.com/vite-pwa/vite-plugin-pwa/commit/92f7959) #####     [View changes on GitHub](https://github.com/vite-pwa/vite-plugin-pwa/compare/v0.16.4...v0.16.5) </details> <details> <summary>vitest-dev/vitest (vitest)</summary> ### [`v0.34.4`](https://github.com/vitest-dev/vitest/releases/tag/v0.34.4) [Compare Source](https://github.com/vitest-dev/vitest/compare/v0.34.3...v0.34.4) #####    🐞 Bug Fixes - Resolving dep optimizer issues with workspace  -  by [@&#8203;thebanjomatic](https://github.com/thebanjomatic) in https://github.com/vitest-dev/vitest/issues/4036 [<samp>(0c13c)</samp>](https://github.com/vitest-dev/vitest/commit/0c13c39c) - Don't process config file twice  -  by [@&#8203;sheremet-va](https://github.com/sheremet-va) in https://github.com/vitest-dev/vitest/issues/4077 [<samp>(a84a8)</samp>](https://github.com/vitest-dev/vitest/commit/a84a8e05) - **coverage**: - Log info only when terminal reporter is used  -  by [@&#8203;AriPerkkio](https://github.com/AriPerkkio) in https://github.com/vitest-dev/vitest/issues/4027 [<samp>(9f043)</samp>](https://github.com/vitest-dev/vitest/commit/9f04386b) - **happy-dom**: - Use the nodejs console in happy-dom v11  -  by [@&#8203;capricorn86](https://github.com/capricorn86) in https://github.com/vitest-dev/vitest/issues/4090 [<samp>(59434)</samp>](https://github.com/vitest-dev/vitest/commit/59434189) - **runner**: - Incorrect test name pattern matching  -  by [@&#8203;Dunqing](https://github.com/Dunqing) in https://github.com/vitest-dev/vitest/issues/4071 [<samp>(b5bf3)</samp>](https://github.com/vitest-dev/vitest/commit/b5bf3290) - **vite-node**: - Check more precisely for root/base paths  -  by [@&#8203;danielroe](https://github.com/danielroe) in https://github.com/vitest-dev/vitest/issues/4049 [<samp>(80741)</samp>](https://github.com/vitest-dev/vitest/commit/807418fa) - **vitest**: - "vi" doesn't rely on context  -  by [@&#8203;sheremet-va](https://github.com/sheremet-va) in https://github.com/vitest-dev/vitest/issues/4031 [<samp>(0d0f3)</samp>](https://github.com/vitest-dev/vitest/commit/0d0f35f6) - Only override ssr.optimizer instead of the whole ssr object  -  by [@&#8203;sheremet-va](https://github.com/sheremet-va) in https://github.com/vitest-dev/vitest/issues/4080 [<samp>(410bc)</samp>](https://github.com/vitest-dev/vitest/commit/410bc454) - Don't start the server when optimizer is enabled  -  by [@&#8203;sheremet-va](https://github.com/sheremet-va) in https://github.com/vitest-dev/vitest/issues/4095 [<samp>(00e81)</samp>](https://github.com/vitest-dev/vitest/commit/00e81122) - Set SSR env only when transformMode is ssr  -  by [@&#8203;sheremet-va](https://github.com/sheremet-va) in https://github.com/vitest-dev/vitest/issues/4083 [<samp>(f8ea7)</samp>](https://github.com/vitest-dev/vitest/commit/f8ea716a) - Show error when calling API on files that user has no access to  -  by [@&#8203;sheremet-va](https://github.com/sheremet-va) in https://github.com/vitest-dev/vitest/issues/4085 [<samp>(8b39c)</samp>](https://github.com/vitest-dev/vitest/commit/8b39c117) - **web-worker**: - Don't rely on browser API when it's not provided  -  by [@&#8203;sheremet-va](https://github.com/sheremet-va) in https://github.com/vitest-dev/vitest/issues/4014 [<samp>(e78a4)</samp>](https://github.com/vitest-dev/vitest/commit/e78a449d) #####     [View changes on GitHub](https://github.com/vitest-dev/vitest/compare/v0.34.3...v0.34.4) </details> <details> <summary>vuejs/language-tools (vue-tsc)</summary> ### [`v1.8.11`](https://github.com/vuejs/language-tools/blob/HEAD/CHANGELOG.md#1811-2023913) [Compare Source](https://github.com/vuejs/language-tools/compare/v1.8.10...v1.8.11) - feat: slot references codeLens counting fragment default slot ([#&#8203;932](https://github.com/vuejs/language-tools/issues/932)) - fix: correct message for `@vue-expect-error` ([#&#8203;3541](https://github.com/vuejs/language-tools/issues/3541)) - thanks [@&#8203;so1ve](https://github.com/so1ve) - fix: avoid global macros conflicts with local variables ([#&#8203;3550](https://github.com/vuejs/language-tools/issues/3550)) - thanks [@&#8203;so1ve](https://github.com/so1ve) - fix: script setup comments at top breaks global macros ([#&#8203;3549](https://github.com/vuejs/language-tools/issues/3549)) - thanks [@&#8203;so1ve](https://github.com/so1ve) - fix(vue-tsc): prevent rebuild in incremental mode throwing error ([#&#8203;3556](https://github.com/vuejs/language-tools/issues/3556)) - thanks [@&#8203;blake-newman](https://github.com/blake-newman) ##### Full-time Support by <table> <tbody> <tr> <td> <a href="https://stackblitz.com/"><img src="https://raw.githubusercontent.com/vuejs/language-tools/HEAD/.github/sponsors/StackBlitz.png" height="80" /></a> </td> <td><h4><a href="https://blog.stackblitz.com/posts/webcontainer-api-is-here/">WebContainer API is here.</a></h4></td> </tr> </tbody> </table> ##### Our Platinum Sponsors <table> <tbody> <tr> <td> <a href="https://nuxt.com/"><img src="https://raw.githubusercontent.com/vuejs/language-tools/HEAD/.github/sponsors/nuxt.svg" height="60" /></a> </td> <td>The Intuitive Web Framework</td> </tr> <tr> <td> <a href="https://vuejs.org/"><img src="https://raw.githubusercontent.com/vuejs/language-tools/HEAD/.github/sponsors/vue.png" height="80" /></a> </td> <td>The Progressive JavaScript Framework</td> </tr> </tbody> </table> ##### Our Silver Sponsors <table> <tbody> <tr> <td> <p align="center"> <a href="https://www.prefect.io/"><img src="https://raw.githubusercontent.com/vuejs/language-tools/HEAD/.github/sponsors/prefect.svg" height="40" /></a> </p> </td> </tr> </tbody> </table> <h5> Add you via <a href="https://github.com/sponsors/johnsoncodehk">GitHub Sponsors</a> or <a href="https://opencollective.com/volarjs">Open Collective</a> </h5> </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:eyJjcmVhdGVkSW5WZXIiOiIzNi42NS4xIiwidXBkYXRlZEluVmVyIjoiMzYuNjUuMSIsInRhcmdldEJyYW5jaCI6Im1haW4ifQ==-->
renovate added the
dependencies
 label 2023-09-14 00:10:01 +00:00
renovate force-pushed renovate/dev-dependencies from e6aeee6fcb to 336b3b2ba2 2023-09-14 01:09:43 +00:00 Compare
renovate force-pushed renovate/dev-dependencies from 336b3b2ba2 to 5a96142e1f 2023-09-14 02:09:03 +00:00 Compare
renovate force-pushed renovate/dev-dependencies from 5a96142e1f to 1245807ab6 2023-09-14 07:09:11 +00:00 Compare
renovate force-pushed renovate/dev-dependencies from 1245807ab6 to 9fa34de1ee 2023-09-14 16:09:32 +00:00 Compare
renovate force-pushed renovate/dev-dependencies from 9fa34de1ee to b38c7cd33d 2023-09-15 01:10:55 +00:00 Compare
renovate force-pushed renovate/dev-dependencies from b38c7cd33d to 6d36de54f3 2023-09-15 09:09:51 +00:00 Compare
konrad added 1 commit 2023-09-15 10:57:56 +00:00
continuous-integration/drone/pr Build is passing Details
ae6ed2061f
chore(deps): update lockfile
konrad scheduled this pull request to auto merge when all checks succeed 2023-09-15 10:58:12 +00:00
frederick commented 2023-09-15 11:09:08 +00:00
Member
Copy Link

Hi renovate!

Thank you for creating a PR!

I've deployed the changes of this PR on a preview environment under this URL: https://3746-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 somehwere. The easiest to use is https://try.vikunja.io/.

Have a nice day!

Beep boop, I'm a bot.

Hi renovate! Thank you for creating a PR! I've deployed the changes of this PR on a preview environment under this URL: https://3746-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 somehwere. The easiest to use is https://try.vikunja.io/. Have a nice day! > Beep boop, I'm a bot.
renovate commented 2023-09-15 11:09:23 +00:00
Author
Member
Copy Link

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.

### 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.
konrad merged commit 0235b14997 into main 2023-09-15 11:59:32 +00:00
This repo is archived. You cannot comment on pull requests.
Reviewers
No reviewers
Labels
Clear labels   
area/internal-code

   
changes requested

   
confirmed

   
dependencies

   
duplicate

This issue or pull request already exists

  
good first issue

   
help wanted

Need some help

  
hosting

   
invalid

Something is wrong

  
kind/bug

Something is not working

  
kind/feature

New feature

  
question

More information is needed

  
wontfix

This won't be fixed

No Label
area/internal-code
changes requested
confirmed
dependencies
duplicate
good first issue
help wanted
hosting
invalid
kind/bug
kind/feature
question
wontfix
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
3 Participants
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/frontend#3746
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?