chore(deps): update devdependencies

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@types/markdown-it (source)	~13.0.6 -> ~13.0.7
@types/node (source)	~20.9.2 -> ~20.10.0
@types/sanitize-html (source)	~2.9.4 -> ~2.9.5
@types/semver (source)	~7.5.5 -> ~7.5.6
@types/validator (source)	~13.11.6 -> ~13.11.7
cypress (source)	~13.5.1 -> ~13.6.0
esbuild	~0.19.6 -> ~0.19.8
tsx	~3.13.0 -> ~3.14.0
vue (source)	~3.3.8 -> ~3.3.9

---

Release Notes

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.8

Compare Source

• Add a treemap chart to esbuild's bundle analyzer (#​2848)

  The bundler analyzer on esbuild's website (https://esbuild.github.io/analyze/) now has a treemap chart type in addition to the two existing chart types (sunburst and flame). This should be more familiar for people coming from other similar tools, as well as make better use of large screens.

• Allow decorators after the export keyword (#​104)

  Previously esbuild's decorator parser followed the original behavior of TypeScript's experimental decorators feature, which only allowed decorators to come before the export keyword. However, the upcoming JavaScript decorators feature also allows decorators to come after the export keyword. And with TypeScript 5.0, TypeScript now also allows experimental decorators to come after the export keyword too. So esbuild now allows this as well:

  // This old syntax has always been permitted:
  @​decorator export class Foo {}
  @​decorator export default class Foo {}
  
  // This new syntax is now permitted too:
  export @​decorator class Foo {}
  export default @​decorator class Foo {}

  In addition, esbuild's decorator parser has been rewritten to fix several subtle and likely unimportant edge cases with esbuild's parsing of exports and decorators in TypeScript (e.g. TypeScript apparently does automatic semicolon insertion after interface and export interface but not after export default interface).

• Pretty-print decorators using the same whitespace as the original

  When printing code containing decorators, esbuild will now try to respect whether the original code contained newlines after the decorator or not. This can make generated code containing many decorators much more compact to read:

  // Original code
  class Foo {
    @​a @​b @​c abc
    @​x @​y @​z xyz
  }
  
  // Old output
  class Foo {
    @​a
    @​b
    @​c
    abc;
    @​x
    @​y
    @​z
    xyz;
  }
  
  // New output
  class Foo {
    @​a @​b @​c abc;
    @​x @​y @​z xyz;
  }

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.

privatenumber/tsx (tsx)

v3.14.0

Compare Source

Bug Fixes

• cache: scope cache directory to user (#​332) (7e916f5)

Features

• support Node v20.6.0 module.register() & --import flag (#​337) (23e4694)

---

This release is also available on:

• npm package (@​latest dist-tag)

vuejs/core (vue)

v3.3.9

Compare Source

Bug Fixes

• compiler-core: avoid rewriting scope variables in inline for loops (#​7245) (a2d810e), closes #​7238
• compiler-core: fix resolveParserPlugins decorators check (#​9566) (9d0eba9), closes #​9560
• compiler-sfc: consistently escape type-only prop names (#​8654) (3e08d24), closes #​8635 #​8910 vitejs/vite-plugin-vue#184
• compiler-sfc: malformed filename on windows using path.posix.join() (#​9478) (f18a174), closes #​8671 #​9583 #​9446 #​9473
• compiler-sfc: support :is and :where selector in scoped css rewrite (#​8929) (3227e50)
• compiler-sfc: support resolve extends interface for defineEmits (#​8470) (9e1b74b), closes #​8465
• hmr/transition: fix kept-alive component inside transition disappearing after hmr (#​7126) (d11e978), closes #​7121
• hydration: force hydration for v-bind with .prop modifier (364f319), closes #​7490
• hydration: properly hydrate indeterminate prop (34b5a5d), closes #​7476
• reactivity: clear method on readonly collections should return undefined (#​7316) (657476d)
• reactivity: onCleanup also needs to be cleaned (#​8655) (73fd810), closes #​5151 #​7695
• ssr: hydration __vnode missing for devtools (#​9328) (5156ac5)
• types: allow falsy value types in StyleValue (#​7954) (17aa92b), closes #​7955
• types: defineCustomElement using defineComponent return type with emits (#​7937) (5d932a8), closes #​7782
• types: fix unref and toValue when input union type contains ComputedRef (#​8748) (176d476), closes #​8747 #​8857
• types: fix instance type when props type is incompatible with setup returned type (#​7338) (0e1e8f9), closes #​5885
• types: fix shallowRef return type with union value type (#​7853) (7c44800), closes #​7852
• types: more precise types for class bindings (#​8012) (46e3374)
• types: remove optional properties from defineProps return type (#​6421) (94c049d), closes #​6420
• types: return type of withDefaults should be readonly (#​8601) (f15debc)
• types: revert class type restrictions (5d077c8), closes #​8012
• types: update jsx type definitions (#​8607) (58e2a94)
• types: widen ClassValue type (2424013)
• v-model: avoid overwriting number input with same value (#​7004) (40f4b77), closes #​7003
• v-model: unnecessary value binding error should apply to dynamic instead of static binding (2859b65), closes #​3596

---

Configuration

📅 Schedule: Branch creation - "before 4am on Monday" (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 Mend Renovate. View repository job log here.

[codecov]

Codecov Report

Merging #2561 (bbd10ef) into next (3c5ceec) will decrease coverage by 0.02%.
The diff coverage is n/a.

Additional details and impacted files

@@            Coverage Diff             @@
##             next    #2561      +/-   ##
==========================================
- Coverage   99.57%   99.56%   -0.02%     
==========================================
  Files        2805     2805              
  Lines      250166   250166              
  Branches     1106     1098       -8     
==========================================
- Hits       249105   249074      -31     
- Misses       1033     1064      +31     
  Partials       28       28              

see 1 file with indirect coverage changes

[renovate]

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.