chore(deps): update all non-major dependencies

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@sveltejs/kit (source)	^2.5.7 -> ^2.5.8
@types/node (source)	^20.12.8 -> ^20.12.12
@typescript-eslint/eslint-plugin (source)	^7.8.0 -> ^7.9.0
@typescript-eslint/parser (source)	^7.8.0 -> ^7.9.0
esbuild	^0.20.2 -> ^0.21.3
eslint-plugin-n	^17.4.0 -> ^17.7.0
eslint-plugin-svelte (source)	^2.38.0 -> ^2.39.0
playwright-core (source)	~1.43.1 -> ~1.44.0
sass	^1.76.0 -> ^1.77.1
svelte (source)	^5.0.0-next.123 -> ^5.0.0-next.135

---

Release Notes

sveltejs/kit (@​sveltejs/kit)

v2.5.8

Compare Source

Patch Changes

• fix: prevent excessive Vite dependency optimizations on navigation (#​12182)

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

v7.9.0

Compare Source

🩹 Fixes

• eslint-plugin: [explicit-function-return-types] fix false positive on default parameters

❤️ Thank You

• Kirk Waiblinger
• Sheetal Nandi
• Vinccool96

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

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

v7.9.0

Compare Source

This was a version bump only for parser to align it with other projects, there were no code changes.

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

evanw/esbuild (esbuild)

v0.21.3

Compare Source

• Implement the decorator metadata proposal (#​3760)

  This release implements the decorator metadata proposal, which is a sub-proposal of the decorators proposal. Microsoft shipped the decorators proposal in TypeScript 5.0 and the decorator metadata proposal in TypeScript 5.2, so it's important that esbuild also supports both of these features. Here's a quick example:

  // Shim the "Symbol.metadata" symbol
  Symbol.metadata ??= Symbol('Symbol.metadata')
  
  const track = (_, context) => {
    (context.metadata.names ||= []).push(context.name)
  }
  
  class Foo {
    @​track foo = 1
    @​track bar = 2
  }
  
  // Prints ["foo", "bar"]
  console.log(Foo[Symbol.metadata].names)

  ⚠️ WARNING ⚠️

  This proposal has been marked as "stage 3" which means "recommended for implementation". However, it's still a work in progress and isn't a part of JavaScript yet, so keep in mind that any code that uses JavaScript decorator metadata may need to be updated as the feature continues to evolve. If/when that happens, I will update esbuild's implementation to match the specification. I will not be supporting old versions of the specification.

• Fix bundled decorators in derived classes (#​3768)

  In certain cases, bundling code that uses decorators in a derived class with a class body that references its own class name could previously generate code that crashes at run-time due to an incorrect variable name. This problem has been fixed. Here is an example of code that was compiled incorrectly before this fix:

  class Foo extends Object {
    @​(x => x) foo() {
      return Foo
    }
  }
  console.log(new Foo().foo())

• Fix tsconfig.json files inside symlinked directories (#​3767)

  This release fixes an issue with a scenario involving a tsconfig.json file that extends another file from within a symlinked directory that uses the paths feature. In that case, the implicit baseURL value should be based on the real path (i.e. after expanding all symbolic links) instead of the original path. This was already done for other files that esbuild resolves but was not yet done for tsconfig.json because it's special-cased (the regular path resolver can't be used because the information inside tsconfig.json is involved in path resolution). Note that this fix no longer applies if the --preserve-symlinks setting is enabled.

v0.21.2

Compare Source

• Correct this in field and accessor decorators (#​3761)

  This release changes the value of this in initializers for class field and accessor decorators from the module-level this value to the appropriate this value for the decorated element (either the class or the instance). It was previously incorrect due to lack of test coverage. Here's an example of a decorator that doesn't work without this change:

  const dec = () => function() { this.bar = true }
  class Foo { @​dec static foo }
  console.log(Foo.bar) // Should be "true"

• Allow es2023 as a target environment (#​3762)

  TypeScript recently added es2023 as a compilation target, so esbuild now supports this too. There is no difference between a target of es2022 and es2023 as far as esbuild is concerned since the 2023 edition of JavaScript doesn't introduce any new syntax features.

v0.21.1

Compare Source

• Fix a regression with --keep-names (#​3756)

  The previous release introduced a regression with the --keep-names setting and object literals with get/set accessor methods, in which case the generated code contained syntax errors. This release fixes the regression:

  // Original code
  x = { get y() {} }
  
  // Output from version 0.21.0 (with --keep-names)
  x = { get y: /* @​__PURE__ */ __name(function() {
  }, "y") };
  
  // Output from this version (with --keep-names)
  x = { get y() {
  } };

v0.21.0

Compare Source

This release doesn't contain any deliberately-breaking changes. However, it contains a very complex new feature and while all of esbuild's tests pass, I would not be surprised if an important edge case turns out to be broken. So I'm releasing this as a breaking change release to avoid causing any trouble. As usual, make sure to test your code when you upgrade.

• Implement the JavaScript decorators proposal (#​104)

  With this release, esbuild now contains an implementation of the upcoming JavaScript decorators proposal. This is the same feature that shipped in TypeScript 5.0 and has been highly-requested on esbuild's issue tracker. You can read more about them in that blog post and in this other (now slightly outdated) extensive blog post here: https://2ality.com/2022/10/javascript-decorators.html. Here's a quick example:

  const log = (fn, context) => function() {
    console.log(`before ${context.name}`)
    const it = fn.apply(this, arguments)
    console.log(`after ${context.name}`)
    return it
  }
  
  class Foo {
    @​log static foo() {
      console.log('in foo')
    }
  }
  
  // Logs "before foo", "in foo", "after foo"
  Foo.foo()

  Note that this feature is different than the existing "TypeScript experimental decorators" feature that esbuild already implements. It uses similar syntax but behaves very differently, and the two are not compatible (although it's sometimes possible to write decorators that work with both). TypeScript experimental decorators will still be supported by esbuild going forward as they have been around for a long time, are very widely used, and let you do certain things that are not possible with JavaScript decorators (such as decorating function parameters). By default esbuild will parse and transform JavaScript decorators, but you can tell esbuild to parse and transform TypeScript experimental decorators instead by setting "experimentalDecorators": true in your tsconfig.json file.

  Probably at least half of the work for this feature went into creating a test suite that exercises many of the proposal's edge cases: https://github.com/evanw/decorator-tests. It has given me a reasonable level of confidence that esbuild's initial implementation is acceptable. However, I don't have access to a significant sample of real code that uses JavaScript decorators. If you're currently using JavaScript decorators in a real code base, please try out esbuild's implementation and let me know if anything seems off.

  ⚠️ WARNING ⚠️

  This proposal has been in the works for a very long time (work began around 10 years ago in 2014) and it is finally getting close to becoming part of the JavaScript language. However, it's still a work in progress and isn't a part of JavaScript yet, so keep in mind that any code that uses JavaScript decorators may need to be updated as the feature continues to evolve. The decorators proposal is pretty close to its final form but it can and likely will undergo some small behavioral adjustments before it ends up becoming a part of the standard. If/when that happens, I will update esbuild's implementation to match the specification. I will not be supporting old versions of the specification.

• Optimize the generated code for private methods

  Previously when lowering private methods for old browsers, esbuild would generate one WeakSet for each private method. This mirrors similar logic for generating one WeakSet for each private field. Using a separate WeakMap for private fields is necessary as their assignment can be observable:

  let it
  class Bar {
    constructor() {
      it = this
    }
  }
  class Foo extends Bar {
    #x = 1
    #y = null.foo
    static check() {
      console.log(#x in it, #y in it)
    }
  }
  try { new Foo } catch {}
  Foo.check()

  This prints true false because this partially-initialized instance has #x but not #y. In other words, it's not true that all class instances will always have all of their private fields. However, the assignment of private methods to a class instance is not observable. In other words, it's true that all class instances will always have all of their private methods. This means esbuild can lower private methods into code where all methods share a single WeakSet, which is smaller, faster, and uses less memory. Other JavaScript processing tools such as the TypeScript compiler already make this optimization. Here's what this change looks like:

  // Original code
  class Foo {
    #x() { return this.#x() }
    #y() { return this.#y() }
    #z() { return this.#z() }
  }
  
  // Old output (--supported:class-private-method=false)
  var _x, x_fn, _y, y_fn, _z, z_fn;
  class Foo {
    constructor() {
      __privateAdd(this, _x);
      __privateAdd(this, _y);
      __privateAdd(this, _z);
    }
  }
  _x = new WeakSet();
  x_fn = function() {
    return __privateMethod(this, _x, x_fn).call(this);
  };
  _y = new WeakSet();
  y_fn = function() {
    return __privateMethod(this, _y, y_fn).call(this);
  };
  _z = new WeakSet();
  z_fn = function() {
    return __privateMethod(this, _z, z_fn).call(this);
  };
  
  // New output (--supported:class-private-method=false)
  var _Foo_instances, x_fn, y_fn, z_fn;
  class Foo {
    constructor() {
      __privateAdd(this, _Foo_instances);
    }
  }
  _Foo_instances = new WeakSet();
  x_fn = function() {
    return __privateMethod(this, _Foo_instances, x_fn).call(this);
  };
  y_fn = function() {
    return __privateMethod(this, _Foo_instances, y_fn).call(this);
  };
  z_fn = function() {
    return __privateMethod(this, _Foo_instances, z_fn).call(this);
  };

• Fix an obscure bug with lowering class members with computed property keys

  When class members that use newer syntax features are transformed for older target environments, they sometimes need to be relocated. However, care must be taken to not reorder any side effects caused by computed property keys. For example, the following code must evaluate a() then b() then c():

  class Foo {
    [a()]() {}
    [b()];
    static { c() }
  }

  Previously esbuild did this by shifting the computed property key forward to the next spot in the evaluation order. Classes evaluate all computed keys first and then all static class elements, so if the last computed key needs to be shifted, esbuild previously inserted a static block at start of the class body, ensuring it came before all other static class elements:

  var _a;
  class Foo {
    constructor() {
      __publicField(this, _a);
    }
    static {
      _a = b();
    }
    [a()]() {
    }
    static {
      c();
    }
  }

  However, this could cause esbuild to accidentally generate a syntax error if the computed property key contains code that isn't allowed in a static block, such as an await expression. With this release, esbuild fixes this problem by shifting the computed property key backward to the previous spot in the evaluation order instead, which may push it into the extends clause or even before the class itself:

  // Original code
  class Foo {
    [a()]() {}
    [await b()];
    static { c() }
  }
  
  // Old output (with --supported:class-field=false)
  var _a;
  class Foo {
    constructor() {
      __publicField(this, _a);
    }
    static {
      _a = await b();
    }
    [a()]() {
    }
    static {
      c();
    }
  }
  
  // New output (with --supported:class-field=false)
  var _a, _b;
  class Foo {
    constructor() {
      __publicField(this, _a);
    }
    [(_b = a(), _a = await b(), _b)]() {
    }
    static {
      c();
    }
  }

• Fix some --keep-names edge cases

  The NamedEvaluation syntax-directed operation in the JavaScript specification gives certain anonymous expressions a name property depending on where they are in the syntax tree. For example, the following initializers convey a name value:

  var foo = function() {}
  var bar = class {}
  console.log(foo.name, bar.name)

  When you enable esbuild's --keep-names setting, esbuild generates additional code to represent this NamedEvaluation operation so that the value of the name property persists even when the identifiers are renamed (e.g. due to minification).

  However, I recently learned that esbuild's implementation of NamedEvaluation is missing a few cases. Specifically esbuild was missing property definitions, class initializers, logical-assignment operators. These cases should now all be handled:

  var obj = { foo: function() {} }
  class Foo0 { foo = function() {} }
  class Foo1 { static foo = function() {} }
  class Foo2 { accessor foo = function() {} }
  class Foo3 { static accessor foo = function() {} }
  foo ||= function() {}
  foo &&= function() {}
  foo ??= function() {}

eslint-community/eslint-plugin-n (eslint-plugin-n)

v17.7.0

Compare Source

🌟 Features

• hashbang: Add support to map extensions to executables (#​278) (3fd7639)
• node-builtin: Add node 20.13.0, 22.0.0, and 22.1.0 support (#​276) (4a685c0)

🩹 Fixes

• node-builtins: Remove "node:" prefix from "ignores" message (#​277) (704f0b9)

📚 Documentation

• node-builtins: Specify that only static properties are supported (#​272) (735a520)
• Provide an example with eslint-plugin-n to Playground (#​275) (cb8ffa6)

v17.6.0

Compare Source

🌟 Features

• Add support for ignoring experemental features (#​269) (c046376)

📚 Documentation

• add maintainance info (#​271) (b454488), closes #​194

v17.5.1

Compare Source

🩹 Fixes

• Add supported version to Buffer constructor (#​266) (030f51b)

v17.5.0

Compare Source

🌟 Features

• import-target: Add resolution error reason (#​264) (982a723)
• node-builtins: Add node globals (#​261) (9466731)

🩹 Fixes

• remove invalid es-builtins (#​258) (ecdf019)

🧹 Chores

• update dependency markdownlint-cli to ^0.40.0 (#​263) (1e41e7c)

sveltejs/eslint-plugin-svelte (eslint-plugin-svelte)

v2.39.0

Compare Source

Minor Changes

• #​749 da4d535 Thanks @​baseballyama! - feat: add svelte/no-svelte-internal rule

• #​758 6ee50c8 Thanks @​ota-meshi! - feat: Update svelte-eslint-parser to 0.36

microsoft/playwright (playwright-core)

v1.44.0

Compare Source

New APIs

Accessibility assertions

• expect(locator).toHaveAccessibleName() checks if the element has the specified accessible name:

  const locator = page.getByRole('button');
  await expect(locator).toHaveAccessibleName('Submit');

• expect(locator).toHaveAccessibleDescription() checks if the element has the specified accessible description:

  const locator = page.getByRole('button');
  await expect(locator).toHaveAccessibleDescription('Upload a photo');

• expect(locator).toHaveRole() checks if the element has the specified ARIA role:

  const locator = page.getByTestId('save-button');
  await expect(locator).toHaveRole('button');

Locator handler

• After executing the handler added with page.addLocatorHandler(), Playwright will now wait until the overlay that triggered the handler is not visible anymore. You can opt-out of this behavior with the new noWaitAfter option.
• You can use new times option in page.addLocatorHandler() to specify maximum number of times the handler should be run.
• The handler in page.addLocatorHandler() now accepts the locator as argument.
• New page.removeLocatorHandler() method for removing previously added locator handlers.

const locator = page.getByText('This interstitial covers the button');
await page.addLocatorHandler(locator, async overlay => {
  await overlay.locator('#close').click();
}, { times: 3, noWaitAfter: true });
// Run your tests that can be interrupted by the overlay.
// ...
await page.removeLocatorHandler(locator);

Miscellaneous options

• multipart option in apiRequestContext.fetch() now accepts FormData and supports repeating fields with the same name.

  const formData = new FormData();
  formData.append('file', new File(['let x = 2024;'], 'f1.js', { type: 'text/javascript' }));
  formData.append('file', new File(['hello'], 'f2.txt', { type: 'text/plain' }));
  context.request.post('https://example.com/uploadFiles', {
    multipart: formData
  });

• expect(callback).toPass({ intervals }) can now be configured by expect.toPass.inervals option globally in testConfig.expect or per project in testProject.expect.

• expect(page).toHaveURL(url) now supports ignoreCase option.

• testProject.ignoreSnapshots allows to configure per project whether to skip screenshot expectations.

Reporter API

• New method suite.entries() returns child test suites and test cases in their declaration order. suite.type and testCase.type can be used to tell apart test cases and suites in the list.
• Blob reporter now allows overriding report file path with a single option outputFile. The same option can also be specified as PLAYWRIGHT_BLOB_OUTPUT_FILE environment variable that might be more convenient on CI/CD.
• JUnit reporter now supports includeProjectInTestName option.

Command line

• --last-failed CLI option for running only tests that failed in the previous run.

  First run all tests:

  $ npx playwright test
  
  Running 103 tests using 5 workers
  ...
  2 failed
    [chromium] › my-test.spec.ts:8:5 › two ─────────────────────────────────────────────────────────
    [chromium] › my-test.spec.ts:13:5 › three ──────────────────────────────────────────────────────
  101 passed (30.0s)

  Now fix the failing tests and run Playwright again with --last-failed option:

  $ npx playwright test --last-failed
  
  Running 2 tests using 2 workers
    2 passed (1.2s)

Browser Versions

• Chromium 125.0.6422.14
• Mozilla Firefox 125.0.1
• WebKit 17.4

This version was also tested against the following stable channels:

• Google Chrome 124
• Microsoft Edge 124

sass/dart-sass (sass)

v1.77.1

Compare Source

• Fix a crash that could come up with importers in certain contexts.

v1.77.0

Compare Source

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

sveltejs/svelte (svelte)

v5.0.0-next.135

Compare Source

Patch Changes

• fix: make messages more consistent (#​11643)

• feat: introduce rootDir compiler option, make filename relative to it (#​11627)

• fix: rename __svelte_meta.filename to __svelte_meta.file to align with svelte 4 (#​11627)

• fix: avoid state_referenced_locally warning within type annotations (#​11638)

v5.0.0-next.134

Compare Source

Patch Changes

• chore: improve SSR invalid element error message (#​11585)

• fix: deduplicate children prop and default slot (#​10800)

• feat: error on imports to svelte/internal/* (#​11632)

• fix: better handle img loading attribute (#​11635)

• feat: add $state.is rune (#​11613)

• feat: provide $state warnings for accidental equality (#​11610)

• feat: error when snippet shadow a prop (#​11631)

• chore: use new CustomEvent instead of deprecated initCustomEvent (#​11629)

v5.0.0-next.133

Compare Source

Patch Changes

• fix: add backwards-compat for old warning codes in legacy mode (#​11607)

v5.0.0-next.132

Compare Source

Patch Changes

• chore: improve runtime overhead of creating comment templates (#​11591)

• fix: replicate Svelte 4 props update detection in legacy mode (#​11577)

• fix: allow for non optional chain call expression in render (#​11578)

• fix: correctly handle falsy values of style directives in SSR mode (#​11583)

• fix: improve handling of lazy image elements (#​11593)

• fix: skip deriveds for props with known safe calls (#​11595)

v5.0.0-next.131

Compare Source

Patch Changes

• chore: optimise effects (#​11569)

• fix: ensure all effect cleanup functions are untracked (#​11567)

v5.0.0-next.130

Compare Source

Patch Changes

• fix: improve internal mechanism for handling process_effects (#​11560)

v5.0.0-next.129

Compare Source

Patch Changes

• fix: further adjust heuristics for effect_update_depth_exceeded (#​11558)

v5.0.0-next.128

Compare Source

Patch Changes

• fix: improved $inspect handling of reactive Map/Set/Date (#​11553)

• fix: adjust heuristics for effect_update_depth_exceeded (#​11557)

v5.0.0-next.127

Compare Source

Patch Changes

• fix: don't warn on writes to $state (#​11540)

• feat: provide better error messages in DEV (#​11526)

• fix: better support for lazy img elements (#​11545)

• fix: handle falsy prop aliases correctly (#​11539)

• fix: ensure spread events are added even when rerunning spread immediately (#​11535)

v5.0.0-next.126

Compare Source

Patch Changes

• fix: improve behaviour of unowned derived signals (#​11521)

• fix: make $effect.active() true when updating deriveds (#​11500)

• fix: skip parent element validation for snippet contents (#​11463)

v5.0.0-next.125

Compare Source

Patch Changes

• fix: coerce incremented/decremented sources (#​11506)

• feat: add support for svelte inspector (#​11514)

• fix: skip AST analysis of TypeScript AST nodes (#​11513)

• fix: use import.meta.hot.acceptExports when available to support partial hmr in vite (#​11453)

• feat: better error for bind:this legacy API usage (#​11498)

---

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.

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