chore(deps): update dev-dependencies #3829

renovate · 2023-11-19T00:15:03Z

renovate commented

2023-11-19 00:15:03 +00:00

This PR contains the following updates:

Package	Type	Update	Change
@rushstack/eslint-patch (source)	devDependencies	minor	`1.5.1` -> `1.6.0`
@types/codemirror (source)	devDependencies	patch	`5.60.13` -> `5.60.15`
@types/node (source)	devDependencies	patch	`20.9.1` -> `20.9.4`
@types/sortablejs (source)	devDependencies	patch	`1.15.5` -> `1.15.7`
@typescript-eslint/eslint-plugin	devDependencies	minor	`6.11.0` -> `6.12.0`
@typescript-eslint/parser	devDependencies	minor	`6.11.0` -> `6.12.0`
caniuse-lite	devDependencies	patch	`1.0.30001563` -> `1.0.30001564`
cypress (source)	devDependencies	minor	`13.5.1` -> `13.6.0`
esbuild	devDependencies	patch	`0.19.5` -> `0.19.7`
rollup (source)	devDependencies	patch	`4.5.0` -> `4.5.1`
typescript (source)	devDependencies	minor	`5.2.2` -> `5.3.2`
vite-plugin-pwa	devDependencies	minor	`0.16.7` -> `0.17.0`

Release Notes

microsoft/rushstack (@rushstack/eslint-patch)

`v1.6.0`

Compare Source

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

`v6.12.0`

Compare Source

Bug Fixes

eslint-plugin: [class-methods-use-this] detect a problematic case for private/protected members if ignoreClassesThatImplementAnInterface is set (#7705) (155aa1f)
eslint-plugin: [no-unnecessary-condition] fix false positive with computed member access and branded key type (#7706) (f151b26)
eslint-plugin: [switch-exhaustiveness-check] enum members with new line or single quotes are not being fixed correctly (#7806) (a034d0a), closes #7768

Features

member-ordering] add accessor support for member-ordering ([#&#8203;7927](https://github.com/typescript-eslint/typescript-eslint/issues/7927)) ([3c8312d](https://github.com/typescript-eslint/typescript-eslint/commit/3c8312d1e135dc65fa41f629993cd03ed82e3255))

eslint-plugin: [switch-exhaustiveness-check] add requireDefaultForNonUnion option (#7880) (4cfcd45)

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

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

`v6.12.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.30001564`

Compare Source

cypress-io/cypress (cypress)

`v13.6.0`

Compare Source

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

evanw/esbuild (esbuild)

`v0.19.7`

Compare Source

Add support for bundling code that uses import attributes (#3384)

JavaScript is gaining new syntax for associating a map of string key-value pairs with individual ESM imports. The proposal is still a work in progress and is still undergoing significant changes before being finalized. However, the first iteration has already been shipping in Chromium-based browsers for a while, and the second iteration has landed in V8 and is now shipping in node, so it makes sense for esbuild to support it. Here are the two major iterations of this proposal (so far):
1. Import assertions (deprecated, will not be standardized)
  - Uses the assert keyword
  - Does not affect module resolution
  - Causes an error if the assertion fails
  - Shipping in Chrome 91+ (and in esbuild 0.11.22+)
2. Import attributes (currently set to become standardized)
  - Uses the with keyword
  - Affects module resolution
  - Unknown attributes cause an error
  - Shipping in node 21+
You can already use esbuild to bundle code that uses import assertions (the first iteration). However, this feature is mostly useless for bundlers because import assertions are not allowed to affect module resolution. It's basically only useful as an annotation on external imports, which esbuild will then preserve in the output for use in a browser (which would otherwise refuse to load certain imports).

With this release, esbuild now supports bundling code that uses import attributes (the second iteration). This is much more useful for bundlers because they are allowed to affect module resolution, which means the key-value pairs can be provided to plugins. Here's an example, which uses esbuild's built-in support for the upcoming JSON module standard:
```
// On static imports
import foo from './package.json' with { type: 'json' }
console.log(foo)

// On dynamic imports
const bar = await import('./package.json', { with: { type: 'json' } })
console.log(bar)
```
One important consequence of the change in semantics between import assertions and import attributes is that two imports with identical paths but different import attributes are now considered to be different modules. This is because the import attributes are provided to the loader, which might then use those attributes during loading. For example, you could imagine an image loader that produces an image of a different size depending on the import attributes.

Import attributes are now reported in the metafile and are now provided to on-load plugins as a map in the with property. For example, here's an esbuild plugin that turns all imports with a type import attribute equal to 'cheese' into a module that exports the cheese emoji:
```
const cheesePlugin = {
  name: 'cheese',
  setup(build) {
    build.onLoad({ filter: /.*/ }, args => {
      if (args.with.type === 'cheese') return {
        contents: `export default "🧀"`,
      }
    })
  }
}

require('esbuild').build({
  bundle: true,
  write: false,
  stdin: {
    contents: `
      import foo from 'data:text/javascript,' with { type: 'cheese' }
      console.log(foo)
    `,
  },
  plugins: [cheesePlugin],
}).then(result => {
  const code = new Function(result.outputFiles[0].text)
  code()
})
```
Warning: It's possible that the second iteration of this feature may change significantly again even though it's already shipping in real JavaScript VMs (since it has already happened once before). In that case, esbuild may end up adjusting its implementation to match the eventual standard behavior. So keep in mind that by using this, you are using an unstable upcoming JavaScript feature that may undergo breaking changes in the future.
Adjust TypeScript experimental decorator behavior (#3230, #3326, #3394)

With this release, esbuild will now allow TypeScript experimental decorators to access both static class properties and #private class names. For example:
```
const check =
  <T,>(a: T, b: T): PropertyDecorator =>
    () => console.log(a === b)

async function test() {
  class Foo {
    static #foo = 1
    static bar = 1 + Foo.#foo
    @&#8203;check(Foo.#foo, 1) a: any
    @&#8203;check(Foo.bar, await Promise.resolve(2)) b: any
  }
}

test().then(() => console.log('pass'))
```
This will now print true true pass when compiled by esbuild. Previously esbuild evaluated TypeScript decorators outside of the class body, so it didn't allow decorators to access Foo or #foo. Now esbuild does something different, although it's hard to concisely explain exactly what esbuild is doing now (see the background section below for more information).

Note that TypeScript's experimental decorator support is currently buggy: TypeScript's compiler passes this test if only the first @check is present or if only the second @check is present, but TypeScript's compiler fails this test if both checks are present together. I haven't changed esbuild to match TypeScript's behavior exactly here because I'm waiting for TypeScript to fix these bugs instead.

Some background: TypeScript experimental decorators don't have consistent semantics regarding the context that the decorators are evaluated in. For example, TypeScript will let you use await within a decorator, which implies that the decorator runs outside the class body (since await isn't supported inside a class body), but TypeScript will also let you use #private names, which implies that the decorator runs inside the class body (since #private names are only supported inside a class body). The value of this in a decorator is also buggy (the run-time value of this changes if any decorator in the class uses a #private name but the type of this doesn't change, leading to the type checker no longer matching reality). These inconsistent semantics make it hard for esbuild to implement this feature as decorator evaluation happens in some superposition of both inside and outside the class body that is particular to the internal implementation details of the TypeScript compiler.
Forbid --keep-names when targeting old browsers (#3477)

The --keep-names setting needs to be able to assign to the name property on functions and classes. However, before ES6 this property was non-configurable, and attempting to assign to it would throw an error. So with this release, esbuild will no longer allow you to enable this setting while also targeting a really old browser.

`v0.19.6`

Compare Source

Fix a constant folding bug with bigint equality

This release fixes a bug where esbuild incorrectly checked for bigint equality by checking the equality of the bigint literal text. This is correct if the bigint doesn't have a radix because bigint literals without a radix are always in canonical form (since leading zeros are not allowed). However, this is incorrect if the bigint has a radix (e.g. 0x123n) because the canonical form is not enforced when a radix is present.
```
// Original code
console.log(!!0n, !!1n, 123n === 123n)
console.log(!!0x0n, !!0x1n, 123n === 0x7Bn)

// Old output
console.log(false, true, true);
console.log(true, true, false);

// New output
console.log(false, true, true);
console.log(!!0x0n, !!0x1n, 123n === 0x7Bn);
```

Add some improvements to the JavaScript minifier

This release adds more cases to the JavaScript minifier, including support for inlining String.fromCharCode and String.prototype.charCodeAt when possible:

// Original code
document.onkeydown = e => e.keyCode === 'A'.charCodeAt(0) && console.log(String.fromCharCode(55358, 56768))

// Old output (with --minify)
document.onkeydown=o=>o.keyCode==="A".charCodeAt(0)&&console.log(String.fromCharCode(55358,56768));

// New output (with --minify)
document.onkeydown=o=>o.keyCode===65&&console.log("🧀");

In addition, immediately-invoked function expressions (IIFEs) that return a single expression are now inlined when minifying. This makes it possible to use IIFEs in combination with @__PURE__ annotations to annotate arbitrary expressions as side-effect free without the IIFE wrapper impacting code size. For example:

// Original code
const sideEffectFreeOffset = /* @&#8203;__PURE__ */ (() => computeSomething())()
use(sideEffectFreeOffset)

// Old output (with --minify)
const e=(()=>computeSomething())();use(e);

// New output (with --minify)
const e=computeSomething();use(e);

Automatically prefix the mask-composite CSS property for WebKit (#3493)

The mask-composite property will now be prefixed as -webkit-mask-composite for older WebKit-based browsers. In addition to prefixing the property name, handling older browsers also requires rewriting the values since WebKit uses non-standard names for the mask composite modes:

/* Original code */
div {
  mask-composite: add, subtract, intersect, exclude;
}

/* New output (with --target=chrome100) */
div {
  -webkit-mask-composite:
    source-over,
    source-out,
    source-in,
    xor;
  mask-composite:
    add,
    subtract,
    intersect,
    exclude;
}

Avoid referencing this from JSX elements in derived class constructors (#3454)

When you enable --jsx=automatic and --jsx-dev, the JSX transform is supposed to insert this as the last argument to the jsxDEV function. I'm not sure exactly why this is and I can't find any specification for it, but in any case this causes the generated code to crash when you use a JSX element in a derived class constructor before the call to super() as this is not allowed to be accessed at that point. For example
```
// Original code
class ChildComponent extends ParentComponent {
  constructor() {
    super(<div />)
  }
}

// Problematic output (with --loader=jsx --jsx=automatic --jsx-dev)
import { jsxDEV } from "react/jsx-dev-runtime";
class ChildComponent extends ParentComponent {
  constructor() {
    super(/* @&#8203;__PURE__ */ jsxDEV("div", {}, void 0, false, {
      fileName: "<stdin>",
      lineNumber: 3,
      columnNumber: 15
    }, this)); // The reference to "this" crashes here
  }
}
```
The TypeScript compiler doesn't handle this at all while the Babel compiler just omits this for the entire constructor (even after the call to super()). There seems to be no specification so I can't be sure that this change doesn't break anything important. But given that Babel is pretty loose with this and TypeScript doesn't handle this at all, I'm guessing this value isn't too important. React's blog post seems to indicate that this value was intended to be used for a React-specific migration warning at some point, so it could even be that this value is irrelevant now. Anyway the crash in this case should now be fixed.
Allow package subpath imports to map to node built-ins (#3485)

You are now able to use a subpath import in your package to resolve to a node built-in module. For example, with a package.json file like this:
```
{
  "type": "module",
  "imports": {
    "#stream": {
      "node": "stream",
      "default": "./stub.js"
    }
  }
}
```
You can now import from node's stream module like this:
```
import * as stream from '#stream';
console.log(Object.keys(stream));
```
This will import from node's stream module when the platform is node and from ./stub.js otherwise.
No longer throw an error when a Symbol is missing (#3453)

Certain JavaScript syntax features use special properties on the global Symbol object. For example, the asynchronous iteration syntax uses Symbol.asyncIterator. Previously esbuild's generated code for older browsers required this symbol to be polyfilled. However, starting with this release esbuild will use Symbol.for() to construct these symbols if they are missing instead of throwing an error about a missing polyfill. This means your code no longer needs to include a polyfill for missing symbols as long as your code also uses Symbol.for() for missing symbols.
Parse upcoming changes to TypeScript syntax (#3490, #3491)

With this release, you can now use from as the name of a default type-only import in TypeScript code, as well as of as the name of an await using loop iteration variable:
```
import type from from 'from'
for (await using of of of) ;
```
This matches similar changes in the TypeScript compiler (#56376 and #55555) which will start allowing this syntax in an upcoming version of TypeScript. Please never actually write code like this.

The type-only import syntax change was contributed by @magic-akari.

rollup/rollup (rollup)

`v4.5.1`

Compare Source

2023-11-21

Bug Fixes

Do not error when a function expression uses the same name for a parameter and its id (#5262)

Pull Requests

#5257: Fix graphs in docs, improve REPL colors (@lukastaegert)
#5262: Allow function expression parameters to shadow the function id (@lukastaegert)

Microsoft/TypeScript (typescript)

`v5.3.2`: TypeScript 5.3

Compare Source

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

Downloads are available on:

NuGet package

vite-pwa/vite-plugin-pwa (vite-plugin-pwa)

`v0.17.0`

Compare Source

🚨 Breaking Changes

Support Vite 5 - by @userquin in https://github.com/vite-pwa/vite-plugin-pwa/issues/598 (54b7a)

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 | |---|---|---|---| | [@rushstack/eslint-patch](https://rushstack.io) ([source](https://github.com/microsoft/rushstack)) | devDependencies | minor | [`1.5.1` -> `1.6.0`](https://renovatebot.com/diffs/npm/@rushstack%2feslint-patch/1.5.1/1.6.0) | | [@types/codemirror](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/codemirror) ([source](https://github.com/DefinitelyTyped/DefinitelyTyped)) | devDependencies | patch | [`5.60.13` -> `5.60.15`](https://renovatebot.com/diffs/npm/@types%2fcodemirror/5.60.13/5.60.15) | | [@types/node](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/node) ([source](https://github.com/DefinitelyTyped/DefinitelyTyped)) | devDependencies | patch | [`20.9.1` -> `20.9.4`](https://renovatebot.com/diffs/npm/@types%2fnode/20.9.1/20.9.4) | | [@types/sortablejs](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/sortablejs) ([source](https://github.com/DefinitelyTyped/DefinitelyTyped)) | devDependencies | patch | [`1.15.5` -> `1.15.7`](https://renovatebot.com/diffs/npm/@types%2fsortablejs/1.15.5/1.15.7) | | [@typescript-eslint/eslint-plugin](https://github.com/typescript-eslint/typescript-eslint) | devDependencies | minor | [`6.11.0` -> `6.12.0`](https://renovatebot.com/diffs/npm/@typescript-eslint%2feslint-plugin/6.11.0/6.12.0) | | [@typescript-eslint/parser](https://github.com/typescript-eslint/typescript-eslint) | devDependencies | minor | [`6.11.0` -> `6.12.0`](https://renovatebot.com/diffs/npm/@typescript-eslint%2fparser/6.11.0/6.12.0) | | [caniuse-lite](https://github.com/browserslist/caniuse-lite) | devDependencies | patch | [`1.0.30001563` -> `1.0.30001564`](https://renovatebot.com/diffs/npm/caniuse-lite/1.0.30001563/1.0.30001564) | | [cypress](https://cypress.io) ([source](https://github.com/cypress-io/cypress)) | devDependencies | minor | [`13.5.1` -> `13.6.0`](https://renovatebot.com/diffs/npm/cypress/13.5.1/13.6.0) | | [esbuild](https://github.com/evanw/esbuild) | devDependencies | patch | [`0.19.5` -> `0.19.7`](https://renovatebot.com/diffs/npm/esbuild/0.19.5/0.19.7) | | [rollup](https://rollupjs.org/) ([source](https://github.com/rollup/rollup)) | devDependencies | patch | [`4.5.0` -> `4.5.1`](https://renovatebot.com/diffs/npm/rollup/4.5.0/4.5.1) | | [typescript](https://www.typescriptlang.org/) ([source](https://github.com/Microsoft/TypeScript)) | devDependencies | minor | [`5.2.2` -> `5.3.2`](https://renovatebot.com/diffs/npm/typescript/5.2.2/5.3.2) | | [vite-plugin-pwa](https://github.com/vite-pwa/vite-plugin-pwa) | devDependencies | minor | [`0.16.7` -> `0.17.0`](https://renovatebot.com/diffs/npm/vite-plugin-pwa/0.16.7/0.17.0) | --- ### Release Notes <details> <summary>microsoft/rushstack (@rushstack/eslint-patch)</summary> ### [`v1.6.0`](https://github.com/microsoft/rushstack/compare/ef3017f97bef5b6073999ad22150783aafc84ad1...2840be24a2b498e4998deac4fe47ef325d912dee) [Compare Source](https://github.com/microsoft/rushstack/compare/ef3017f97bef5b6073999ad22150783aafc84ad1...2840be24a2b498e4998deac4fe47ef325d912dee) </details> <details> <summary>typescript-eslint/typescript-eslint (@typescript-eslint/eslint-plugin)</summary> ### [`v6.12.0`](https://github.com/typescript-eslint/typescript-eslint/blob/HEAD/packages/eslint-plugin/CHANGELOG.md#6120-2023-11-20) [Compare Source](https://github.com/typescript-eslint/typescript-eslint/compare/v6.11.0...v6.12.0) ##### Bug Fixes - **eslint-plugin:** \[class-methods-use-this] detect a problematic case for private/protected members if `ignoreClassesThatImplementAnInterface` is set ([#7705](https://github.com/typescript-eslint/typescript-eslint/issues/7705)) ([155aa1f](https://github.com/typescript-eslint/typescript-eslint/commit/155aa1f533d1fe23da3c66f9832343faf4866d85)) - **eslint-plugin:** \[no-unnecessary-condition] fix false positive with computed member access and branded key type ([#7706](https://github.com/typescript-eslint/typescript-eslint/issues/7706)) ([f151b26](https://github.com/typescript-eslint/typescript-eslint/commit/f151b26d2178a617e82ad6a0279e3145e303f4f8)) - **eslint-plugin:** \[switch-exhaustiveness-check] enum members with new line or single quotes are not being fixed correctly ([#7806](https://github.com/typescript-eslint/typescript-eslint/issues/7806)) ([a034d0a](https://github.com/typescript-eslint/typescript-eslint/commit/a034d0a3856aa07bd2d52b557fa33c7a88e9e511)), closes [#7768](https://github.com/typescript-eslint/typescript-eslint/issues/7768) ##### Features - \[member-ordering] add accessor support for member-ordering ([#7927](https://github.com/typescript-eslint/typescript-eslint/issues/7927)) ([3c8312d](https://github.com/typescript-eslint/typescript-eslint/commit/3c8312d1e135dc65fa41f629993cd03ed82e3255)) - **eslint-plugin:** \[switch-exhaustiveness-check] add requireDefaultForNonUnion option ([#7880](https://github.com/typescript-eslint/typescript-eslint/issues/7880)) ([4cfcd45](https://github.com/typescript-eslint/typescript-eslint/commit/4cfcd451efb2563130896e42b45252909932c679)) 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 (@typescript-eslint/parser)</summary> ### [`v6.12.0`](https://github.com/typescript-eslint/typescript-eslint/blob/HEAD/packages/parser/CHANGELOG.md#6120-2023-11-20) [Compare Source](https://github.com/typescript-eslint/typescript-eslint/compare/v6.11.0...v6.12.0) **Note:** Version bump only for package [@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.30001564`](https://github.com/browserslist/caniuse-lite/compare/1.0.30001563...1.0.30001564) [Compare Source](https://github.com/browserslist/caniuse-lite/compare/1.0.30001563...1.0.30001564) </details> <details> <summary>cypress-io/cypress (cypress)</summary> ### [`v13.6.0`](https://github.com/cypress-io/cypress/releases/tag/v13.6.0) [Compare Source](https://github.com/cypress-io/cypress/compare/v13.5.1...v13.6.0) Changelog: https://docs.cypress.io/guides/references/changelog#13-6-0 </details> <details> <summary>evanw/esbuild (esbuild)</summary> ### [`v0.19.7`](https://github.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#0197) [Compare Source](https://github.com/evanw/esbuild/compare/v0.19.6...v0.19.7) - Add support for bundling code that uses import attributes ([#3384](https://github.com/evanw/esbuild/issues/3384)) JavaScript is gaining new syntax for associating a map of string key-value pairs with individual ESM imports. The proposal is still a work in progress and is still undergoing significant changes before being finalized. However, the first iteration has already been shipping in Chromium-based browsers for a while, and the second iteration has landed in V8 and is now shipping in node, so it makes sense for esbuild to support it. Here are the two major iterations of this proposal (so far): 1. Import assertions (deprecated, will not be standardized) - Uses the `assert` keyword - Does *not* affect module resolution - Causes an error if the assertion fails - Shipping in Chrome 91+ (and in esbuild 0.11.22+) 2. Import attributes (currently set to become standardized) - Uses the `with` keyword - Affects module resolution - Unknown attributes cause an error - Shipping in node 21+ You can already use esbuild to bundle code that uses import assertions (the first iteration). However, this feature is mostly useless for bundlers because import assertions are not allowed to affect module resolution. It's basically only useful as an annotation on external imports, which esbuild will then preserve in the output for use in a browser (which would otherwise refuse to load certain imports). With this release, esbuild now supports bundling code that uses import attributes (the second iteration). This is much more useful for bundlers because they are allowed to affect module resolution, which means the key-value pairs can be provided to plugins. Here's an example, which uses esbuild's built-in support for the upcoming [JSON module standard](https://github.com/tc39/proposal-json-modules): ```js // On static imports import foo from './package.json' with { type: 'json' } console.log(foo) // On dynamic imports const bar = await import('./package.json', { with: { type: 'json' } }) console.log(bar) ``` One important consequence of the change in semantics between import assertions and import attributes is that two imports with identical paths but different import attributes are now considered to be different modules. This is because the import attributes are provided to the loader, which might then use those attributes during loading. For example, you could imagine an image loader that produces an image of a different size depending on the import attributes. Import attributes are now reported in the [metafile](https://esbuild.github.io/api/#metafile) and are now provided to [on-load plugins](https://esbuild.github.io/plugins/#on-load) as a map in the `with` property. For example, here's an esbuild plugin that turns all imports with a `type` import attribute equal to `'cheese'` into a module that exports the cheese emoji: ```js const cheesePlugin = { name: 'cheese', setup(build) { build.onLoad({ filter: /.*/ }, args => { if (args.with.type === 'cheese') return { contents: `export default "🧀"`, } }) } } require('esbuild').build({ bundle: true, write: false, stdin: { contents: ` import foo from 'data:text/javascript,' with { type: 'cheese' } console.log(foo) `, }, plugins: [cheesePlugin], }).then(result => { const code = new Function(result.outputFiles[0].text) code() }) ``` Warning: It's possible that the second iteration of this feature may change significantly again even though it's already shipping in real JavaScript VMs (since it has already happened once before). In that case, esbuild may end up adjusting its implementation to match the eventual standard behavior. So keep in mind that by using this, you are using an unstable upcoming JavaScript feature that may undergo breaking changes in the future. - Adjust TypeScript experimental decorator behavior ([#3230](https://github.com/evanw/esbuild/issues/3230), [#3326](https://github.com/evanw/esbuild/issues/3326), [#3394](https://github.com/evanw/esbuild/issues/3394)) With this release, esbuild will now allow TypeScript experimental decorators to access both static class properties and `#private` class names. For example: ```js const check = <T,>(a: T, b: T): PropertyDecorator => () => console.log(a === b) async function test() { class Foo { static #foo = 1 static bar = 1 + Foo.#foo @check(Foo.#foo, 1) a: any @check(Foo.bar, await Promise.resolve(2)) b: any } } test().then(() => console.log('pass')) ``` This will now print `true true pass` when compiled by esbuild. Previously esbuild evaluated TypeScript decorators outside of the class body, so it didn't allow decorators to access `Foo` or `#foo`. Now esbuild does something different, although it's hard to concisely explain exactly what esbuild is doing now (see the background section below for more information). Note that TypeScript's experimental decorator support is currently buggy: TypeScript's compiler passes this test if only the first `@check` is present or if only the second `@check` is present, but TypeScript's compiler fails this test if both checks are present together. I haven't changed esbuild to match TypeScript's behavior exactly here because I'm waiting for TypeScript to fix these bugs instead. Some background: TypeScript experimental decorators don't have consistent semantics regarding the context that the decorators are evaluated in. For example, TypeScript will let you use `await` within a decorator, which implies that the decorator runs outside the class body (since `await` isn't supported inside a class body), but TypeScript will also let you use `#private` names, which implies that the decorator runs inside the class body (since `#private` names are only supported inside a class body). The value of `this` in a decorator is also buggy (the run-time value of `this` changes if any decorator in the class uses a `#private` name but the type of `this` doesn't change, leading to the type checker no longer matching reality). These inconsistent semantics make it hard for esbuild to implement this feature as decorator evaluation happens in some superposition of both inside and outside the class body that is particular to the internal implementation details of the TypeScript compiler. - Forbid `--keep-names` when targeting old browsers ([#3477](https://github.com/evanw/esbuild/issues/3477)) The `--keep-names` setting needs to be able to assign to the `name` property on functions and classes. However, before ES6 this property was non-configurable, and attempting to assign to it would throw an error. So with this release, esbuild will no longer allow you to enable this setting while also targeting a really old browser. ### [`v0.19.6`](https://github.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#0196) [Compare Source](https://github.com/evanw/esbuild/compare/v0.19.5...v0.19.6) - Fix a constant folding bug with bigint equality This release fixes a bug where esbuild incorrectly checked for bigint equality by checking the equality of the bigint literal text. This is correct if the bigint doesn't have a radix because bigint literals without a radix are always in canonical form (since leading zeros are not allowed). However, this is incorrect if the bigint has a radix (e.g. `0x123n`) because the canonical form is not enforced when a radix is present. ```js // Original code console.log(!!0n, !!1n, 123n === 123n) console.log(!!0x0n, !!0x1n, 123n === 0x7Bn) // Old output console.log(false, true, true); console.log(true, true, false); // New output console.log(false, true, true); console.log(!!0x0n, !!0x1n, 123n === 0x7Bn); ``` - Add some improvements to the JavaScript minifier This release adds more cases to the JavaScript minifier, including support for inlining `String.fromCharCode` and `String.prototype.charCodeAt` when possible: ```js // Original code document.onkeydown = e => e.keyCode === 'A'.charCodeAt(0) && console.log(String.fromCharCode(55358, 56768)) // Old output (with --minify) document.onkeydown=o=>o.keyCode==="A".charCodeAt(0)&&console.log(String.fromCharCode(55358,56768)); // New output (with --minify) document.onkeydown=o=>o.keyCode===65&&console.log("🧀"); ``` In addition, immediately-invoked function expressions (IIFEs) that return a single expression are now inlined when minifying. This makes it possible to use IIFEs in combination with `@__PURE__` annotations to annotate arbitrary expressions as side-effect free without the IIFE wrapper impacting code size. For example: ```js // Original code const sideEffectFreeOffset = /* @__PURE__ */ (() => computeSomething())() use(sideEffectFreeOffset) // Old output (with --minify) const e=(()=>computeSomething())();use(e); // New output (with --minify) const e=computeSomething();use(e); ``` - Automatically prefix the `mask-composite` CSS property for WebKit ([#3493](https://github.com/evanw/esbuild/issues/3493)) The `mask-composite` property will now be prefixed as `-webkit-mask-composite` for older WebKit-based browsers. In addition to prefixing the property name, handling older browsers also requires rewriting the values since WebKit uses non-standard names for the mask composite modes: ```css /* Original code */ div { mask-composite: add, subtract, intersect, exclude; } /* New output (with --target=chrome100) */ div { -webkit-mask-composite: source-over, source-out, source-in, xor; mask-composite: add, subtract, intersect, exclude; } ``` - Avoid referencing `this` from JSX elements in derived class constructors ([#3454](https://github.com/evanw/esbuild/issues/3454)) When you enable `--jsx=automatic` and `--jsx-dev`, the JSX transform is supposed to insert `this` as the last argument to the `jsxDEV` function. I'm not sure exactly why this is and I can't find any specification for it, but in any case this causes the generated code to crash when you use a JSX element in a derived class constructor before the call to `super()` as `this` is not allowed to be accessed at that point. For example ```js // Original code class ChildComponent extends ParentComponent { constructor() { super(<div />) } } // Problematic output (with --loader=jsx --jsx=automatic --jsx-dev) import { jsxDEV } from "react/jsx-dev-runtime"; class ChildComponent extends ParentComponent { constructor() { super(/* @__PURE__ */ jsxDEV("div", {}, void 0, false, { fileName: "<stdin>", lineNumber: 3, columnNumber: 15 }, this)); // The reference to "this" crashes here } } ``` The TypeScript compiler doesn't handle this at all while the Babel compiler just omits `this` for the entire constructor (even after the call to `super()`). There seems to be no specification so I can't be sure that this change doesn't break anything important. But given that Babel is pretty loose with this and TypeScript doesn't handle this at all, I'm guessing this value isn't too important. React's blog post seems to indicate that this value was intended to be used for a React-specific migration warning at some point, so it could even be that this value is irrelevant now. Anyway the crash in this case should now be fixed. - Allow package subpath imports to map to node built-ins ([#3485](https://github.com/evanw/esbuild/issues/3485)) You are now able to use a [subpath import](https://nodejs.org/api/packages.html#subpath-imports) in your package to resolve to a node built-in module. For example, with a `package.json` file like this: ```json { "type": "module", "imports": { "#stream": { "node": "stream", "default": "./stub.js" } } } ``` You can now import from node's `stream` module like this: ```js import * as stream from '#stream'; console.log(Object.keys(stream)); ``` This will import from node's `stream` module when the platform is `node` and from `./stub.js` otherwise. - No longer throw an error when a `Symbol` is missing ([#3453](https://github.com/evanw/esbuild/issues/3453)) Certain JavaScript syntax features use special properties on the global `Symbol` object. For example, the asynchronous iteration syntax uses `Symbol.asyncIterator`. Previously esbuild's generated code for older browsers required this symbol to be polyfilled. However, starting with this release esbuild will use [`Symbol.for()`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Symbol/for) to construct these symbols if they are missing instead of throwing an error about a missing polyfill. This means your code no longer needs to include a polyfill for missing symbols as long as your code also uses `Symbol.for()` for missing symbols. - Parse upcoming changes to TypeScript syntax ([#3490](https://github.com/evanw/esbuild/issues/3490), [#3491](https://github.com/evanw/esbuild/pull/3491)) With this release, you can now use `from` as the name of a default type-only import in TypeScript code, as well as `of` as the name of an `await using` loop iteration variable: ```ts import type from from 'from' for (await using of of of) ; ``` This matches similar changes in the TypeScript compiler ([#56376](https://github.com/microsoft/TypeScript/issues/56376) and [#55555](https://github.com/microsoft/TypeScript/issues/55555)) which will start allowing this syntax in an upcoming version of TypeScript. Please never actually write code like this. The type-only import syntax change was contributed by [@magic-akari](https://github.com/magic-akari). </details> <details> <summary>rollup/rollup (rollup)</summary> ### [`v4.5.1`](https://github.com/rollup/rollup/blob/HEAD/CHANGELOG.md#451) [Compare Source](https://github.com/rollup/rollup/compare/v4.5.0...v4.5.1) *2023-11-21* ##### Bug Fixes - Do not error when a function expression uses the same name for a parameter and its id ([#5262](https://github.com/rollup/rollup/issues/5262)) ##### Pull Requests - [#5257](https://github.com/rollup/rollup/pull/5257): Fix graphs in docs, improve REPL colors ([@lukastaegert](https://github.com/lukastaegert)) - [#5262](https://github.com/rollup/rollup/pull/5262): Allow function expression parameters to shadow the function id ([@lukastaegert](https://github.com/lukastaegert)) </details> <details> <summary>Microsoft/TypeScript (typescript)</summary> ### [`v5.3.2`](https://github.com/microsoft/TypeScript/releases/tag/v5.3.2): TypeScript 5.3 [Compare Source](https://github.com/Microsoft/TypeScript/compare/v5.2.2...v5.3.2) For release notes, check out the [release announcement](https://devblogs.microsoft.com/typescript/announcing-typescript-5-3/). For the complete list of fixed issues, check out the - [fixed issues query for Typescript 5.3.0 (Beta)](https://github.com/Microsoft/TypeScript/issues?utf8=%E2%9C%93\&q=milestone%3A%22TypeScript+5.3.0%22+is%3Aclosed+). - [fixed issues query for Typescript 5.3.1 (RC)](https://github.com/Microsoft/TypeScript/issues?utf8=%E2%9C%93\&q=milestone%3A%22TypeScript+5.3.1%22+is%3Aclosed+). - [fixed issues query for Typescript 5.3.2 (Stable)](https://github.com/Microsoft/TypeScript/issues?utf8=%E2%9C%93\&q=milestone%3A%22TypeScript+5.3.2%22+is%3Aclosed+). Downloads are available on: - [NuGet package](https://www.nuget.org/packages/Microsoft.TypeScript.MSBuild) </details> <details> <summary>vite-pwa/vite-plugin-pwa (vite-plugin-pwa)</summary> ### [`v0.17.0`](https://github.com/vite-pwa/vite-plugin-pwa/releases/tag/v0.17.0) [Compare Source](https://github.com/vite-pwa/vite-plugin-pwa/compare/v0.16.7...v0.17.0) ##### 🚨 Breaking Changes - Support Vite 5 - by [@userquin](https://github.com/userquin) in https://github.com/vite-pwa/vite-plugin-pwa/issues/598 [<samp>(54b7a)</samp>](https://github.com/vite-pwa/vite-plugin-pwa/commit/54b7ab9) ##### [View changes on GitHub](https://github.com/vite-pwa/vite-plugin-pwa/compare/v0.16.7...v0.17.0) </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. --- - [ ] 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 added the

dependencies

label 2023-11-19 00:15:03 +00:00

renovate force-pushed renovate/dev-dependencies from 29c87eec8d to fa30372740

2023-11-19 00:15:06 +00:00

Compare

renovate force-pushed renovate/dev-dependencies from fa30372740 to 8cb57ed530

2023-11-19 08:13:17 +00:00

Compare

renovate force-pushed renovate/dev-dependencies from 8cb57ed530 to ee67654955

2023-11-20 20:13:52 +00:00

Compare

renovate force-pushed renovate/dev-dependencies from ee67654955 to 6755cfce45

2023-11-21 00:14:50 +00:00

Compare

renovate force-pushed renovate/dev-dependencies from 6755cfce45 to b5cf8e0f1e

2023-11-21 01:13:24 +00:00

Compare

renovate force-pushed renovate/dev-dependencies from b5cf8e0f1e to 7110572085

2023-11-21 02:13:26 +00:00

Compare

renovate force-pushed renovate/dev-dependencies from 7110572085 to f6d0db88e1

2023-11-21 21:13:47 +00:00

Compare

renovate force-pushed renovate/dev-dependencies from f6d0db88e1 to 14e89c26ef

2023-11-21 22:14:09 +00:00

Compare

renovate force-pushed renovate/dev-dependencies from 14e89c26ef to a5cbe07aa3

2023-11-22 01:14:40 +00:00

Compare

renovate force-pushed renovate/dev-dependencies from a5cbe07aa3 to c0d58e11a6

2023-11-22 02:14:37 +00:00

Compare

renovate force-pushed renovate/dev-dependencies from c0d58e11a6 to 7f81ef6e3c

2023-11-22 07:13:36 +00:00

Compare

konrad added 1 commit 2023-11-22 08:21:27 +00:00

continuous-integration/drone/pr Build is passing Details

a4883dc942

chore(deps): update lockfile

frederick commented

2023-11-22 08:28:22 +00:00

Hi renovate!

Thank you for creating a PR!

I've deployed the changes of this PR on a preview environment under this URL: https://3829-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://3829-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-11-22 09:12:28 +00:00

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 282ec3164b into main

2023-11-22 10:20:29 +00:00

konrad referenced this issue from a commit

2023-11-22 10:20:35 +00:00

chore(deps): update dev-dependencies (#3829)

This repo is archived. You cannot comment on pull requests.

No reviewers