chore(deps): update devdependencies

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@types/node (source)	~20.10.4 -> ~20.10.5
esbuild	~0.19.9 -> ~0.19.10
eslint (source)	~8.55.0 -> ~8.56.0
eslint-plugin-jsdoc	~46.9.0 -> ~46.9.1
eslint-plugin-prettier	~5.0.1 -> ~5.1.0
eslint-plugin-vitest	~0.3.15 -> ~0.3.18
tsx	~3.13.0 -> ~3.14.0
vue (source)	~3.3.11 -> ~3.3.13

---

Release Notes

evanw/esbuild (esbuild)

v0.19.10

Compare Source

• Fix glob imports in TypeScript files (#​3319)

  This release fixes a problem where bundling a TypeScript file containing a glob import could emit a call to a helper function that doesn't exist. The problem happened because esbuild's TypeScript transformation removes unused imports (which is required for correctness, as they may be type-only imports) and esbuild's glob import transformation wasn't correctly marking the imported helper function as used. This wasn't caught earlier because most of esbuild's glob import tests were written in JavaScript, not in TypeScript.

• Fix require() glob imports with bundling disabled (#​3546)

  Previously require() calls containing glob imports were incorrectly transformed when bundling was disabled. All glob imports should only be transformed when bundling is enabled. This bug has been fixed.

• Fix a panic when transforming optional chaining with define (#​3551, #​3554)

  This release fixes a case where esbuild could crash with a panic, which was triggered by using define to replace an expression containing an optional chain. Here is an example:

  // Original code
  console.log(process?.env.SHELL)
  
  // Old output (with --define:process.env={})
  /* panic: Internal error (while parsing "<stdin>") */
  
  // New output (with --define:process.env={})
  var define_process_env_default = {};
  console.log(define_process_env_default.SHELL);

  This fix was contributed by @​hi-ogawa.

• Work around a bug in node's CommonJS export name detector (#​3544)

  The export names of a CommonJS module are dynamically-determined at run time because CommonJS exports are properties on a mutable object. But the export names of an ES module are statically-determined at module instantiation time by using import and export syntax and cannot be changed at run time.

  When you import a CommonJS module into an ES module in node, node scans over the source code to attempt to detect the set of export names that the CommonJS module will end up using. That statically-determined set of names is used as the set of names that the ES module is allowed to import at module instantiation time. However, this scan appears to have bugs (or at least, can cause false positives) because it doesn't appear to do any scope analysis. Node will incorrectly consider the module to export something even if the assignment is done to a local variable instead of to the module-level exports object. For example:

  // confuseNode.js
  exports.confuseNode = function(exports) {
    // If this local is called "exports", node incorrectly
    // thinks this file has an export called "notAnExport".
    exports.notAnExport = function() {
    };
  };

  You can see that node incorrectly thinks the file confuseNode.js has an export called notAnExport when that file is loaded in an ES module context:

  $ node -e 'import("./confuseNode.js").then(console.log)'
  [Module: null prototype] {
    confuseNode: [Function (anonymous)],
    default: { confuseNode: [Function (anonymous)] },
    notAnExport: undefined
  }

  To avoid this, esbuild will now rename local variables that use the names exports and module when generating CommonJS output for the node platform.

• Fix the return value of esbuild's super() shim (#​3538)

  Some people write constructor methods that use the return value of super() instead of using this. This isn't too common because TypeScript doesn't let you do that but it can come up when writing JavaScript. Previously esbuild's class lowering transform incorrectly transformed the return value of super() into undefined. With this release, the return value of super() will now be this instead:

  // Original code
  class Foo extends Object {
    field
    constructor() {
      console.log(typeof super())
    }
  }
  new Foo
  
  // Old output (with --target=es6)
  class Foo extends Object {
    constructor() {
      var __super = (...args) => {
        super(...args);
        __publicField(this, "field");
      };
      console.log(typeof __super());
    }
  }
  new Foo();
  
  // New output (with --target=es6)
  class Foo extends Object {
    constructor() {
      var __super = (...args) => {
        super(...args);
        __publicField(this, "field");
        return this;
      };
      console.log(typeof __super());
    }
  }
  new Foo();

• Terminate the Go GC when esbuild's stop() API is called (#​3552)

  If you use esbuild with WebAssembly and pass the worker: false flag to esbuild.initialize(), then esbuild will run the WebAssembly module on the main thread. If you do this within a Deno test and that test calls esbuild.stop() to clean up esbuild's resources, Deno may complain that a setTimeout() call lasted past the end of the test. This happens when the Go is in the middle of a garbage collection pass and has scheduled additional ongoing garbage collection work. Normally calling esbuild.stop() will terminate the web worker that the WebAssembly module runs in, which will terminate the Go GC, but that doesn't happen if you disable the web worker with worker: false.

  With this release, esbuild will now attempt to terminate the Go GC in this edge case by calling clearTimeout() on these pending timeouts.

• Apply /* @​__NO_SIDE_EFFECTS__ */ on tagged template literals (#​3511)

  Tagged template literals that reference functions annotated with a @__NO_SIDE_EFFECTS__ comment are now able to be removed via tree-shaking if the result is unused. This is a convention from Rollup. Here is an example:

  // Original code
  const html = /* @​__NO_SIDE_EFFECTS__ */ (a, ...b) => ({ a, b })
  html`<a>remove</a>`
  x = html`<b>keep</b>`
  
  // Old output (with --tree-shaking=true)
  const html = /* @&#8203;__NO_SIDE_EFFECTS__ */ (a, ...b) => ({ a, b });
  html`<a>remove</a>`;
  x = html`<b>keep</b>`;
  
  // New output (with --tree-shaking=true)
  const html = /* @&#8203;__NO_SIDE_EFFECTS__ */ (a, ...b) => ({ a, b });
  x = html`<b>keep</b>`;

  Note that this feature currently only works within a single file, so it's not especially useful. This feature does not yet work across separate files. I still recommend using @__PURE__ annotations instead of this feature, as they have wider tooling support. The drawback of course is that @__PURE__ annotations need to be added at each call site, not at the declaration, and for non-call expressions such as template literals you need to wrap the expression in an IIFE (immediately-invoked function expression) to create a call expression to apply the @__PURE__ annotation to.

• Publish builds for IBM AIX PowerPC 64-bit (#​3549)

  This release publishes a binary executable to npm for IBM AIX PowerPC 64-bit, which means that in theory esbuild can now be installed in that environment with npm install esbuild. This hasn't actually been tested yet. If you have access to such a system, it would be helpful to confirm whether or not doing this actually works.

eslint/eslint (eslint)

v8.56.0

Compare Source

Features

• 0dd9704 feat: Support custom severity when reporting unused disable directives (#​17212) (Bryan Mishkin)
• 31a7e3f feat: fix no-restricted-properties false negatives with unknown objects (#​17818) (Arka Pratim Chaudhuri)

Bug Fixes

• 7d5e5f6 fix: TypeError: fs.exists is not a function on read-only file system (#​17846) (Francesco Trotta)
• 74739c8 fix: suggestion with invalid syntax in no-promise-executor-return rule (#​17812) (Bryan Mishkin)

Documentation

• 9007719 docs: update link in ways-to-extend.md (#​17839) (Amel SELMANE)
• 3a22236 docs: Update README (GitHub Actions Bot)
• 54c3ca6 docs: fix migration-guide example (#​17829) (Tanuj Kanti)
• 4391b71 docs: check config comments in rule examples (#​17815) (Francesco Trotta)
• fd28363 docs: remove mention about ESLint stylistic rules in readme (#​17810) (Zwyx)
• 48ed5a6 docs: Update README (GitHub Actions Bot)

Chores

• ba6af85 chore: upgrade @​eslint/js@​8.56.0 (#​17864) (Milos Djermanovic)
• 60a531a chore: package.json update for @​eslint/js release (Jenkins)
• ba87a06 chore: update dependency markdownlint to ^0.32.0 (#​17783) (renovate[bot])
• 9271d10 chore: add GitHub issue template for docs issues (#​17845) (Josh Goldberg ✨)
• 70a686b chore: Convert rule tests to FlatRuleTester (#​17819) (Nicholas C. Zakas)
• f3a599d chore: upgrade eslint-plugin-unicorn to v49.0.0 (#​17837) (唯然)
• 905d4b7 chore: upgrade eslint-plugin-eslint-plugin v5.2.1 (#​17838) (唯然)
• 4d7c3ce chore: update eslint-plugin-n v16.4.0 (#​17836) (唯然)
• fd0c60c ci: unpin Node.js 21.2.0 (#​17821) (Francesco Trotta)

gajus/eslint-plugin-jsdoc (eslint-plugin-jsdoc)

v46.9.1

Compare Source

Bug Fixes

• check-examples: properly replace final extension; fixes #​1172 (b102693)

prettier/eslint-plugin-prettier (eslint-plugin-prettier)

v5.1.0

Compare Source

Minor Changes

• #​616 3856413 Thanks @​BPScott! - Add recommended config for the flat config format.

  If you are using flat config, import the recommended config from eslint-plugin-prettier/recommended. Like the legacy format recommended config, this automatically includes the contents of eslint-config-prettier.

  // eslint.config.js
  const eslintPluginPrettierRecommended = require('eslint-plugin-prettier/recommended');
  
  module.exports = [
    // Any other config imports go at the top
    eslintPluginPrettierRecommended,
  ];

Patch Changes

• #​614 5270877 Thanks @​BPScott! - Add meta block to plugin. This improves debugging and cachebusting when using the new flat config

• #​603 a63a570 Thanks @​filiptammergard! - fix: specify eslint-config-prettier as peer dependency

  It's already added to peerDependenciesMeta as optional, which means it should also be specified in peerDependencies.

veritem/eslint-plugin-vitest (eslint-plugin-vitest)

v0.3.18

Compare Source

Bug Fixes

• no-identical-title: improved internal error handling (6f332c5)

Features

• new rule: setup prefer expect assertions (#​326) (ec2952c)

What's Changed

• Feat(new rules): Implement to have been called with by @​veritem in https://github.com/veritem/eslint-plugin-vitest/pull/325
• feat(new rule): setup prefer expect assertions by @​veritem in https://github.com/veritem/eslint-plugin-vitest/pull/326
• chore(trying to fix expect): expect-expect by @​veritem in https://github.com/veritem/eslint-plugin-vitest/pull/327
• Feat/expect expect issues by @​veritem in https://github.com/veritem/eslint-plugin-vitest/pull/328

Full Changelog: vitest-dev/eslint-plugin-vitest@v0.3.17...v0.3.18

v0.3.17

Compare Source

Bug Fixes

• vitest/require-local-test-context-for-concurrent-snapshots: report for all types of snapshot tests (#​322) (efaf109)

v0.3.16

Compare Source

Bug Fixes

• vitest/no-done-callback: do not report when inside concurrent describe (#​321) (65e8cef)

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

Compare Source

Bug Fixes

• compiler-core: fix v-on with modifiers on inline expression of undefined (#​9866) (bae79dd), closes #​9865
• runtime-dom: cache event handlers by key/modifiers (#​9851) (04d2c05), closes #​9849
• types: extract properties from extended collections (#​9854) (24b1c1d), closes #​9852

v3.3.12

Compare Source

Bug Fixes

• hydration: handle appear transition before patch props (#​9837) (e70f4c4), closes #​9832
• sfc/cssVars: fix loss of CSS v-bind variables when setting inline style with string value (#​9824) (0a387df), closes #​9821
• ssr: fix suspense hydration of fallback content (#​7188) (60415b5)
• types: add xmlns:xlink to SVGAttributes (#​9300) (0d61b42), closes #​9299
• types: fix shallowRef type error (#​9839) (9a57158)
• types: support for generic keyof slots (#​8374) (213eba4)

---

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

All modified and coverable lines are covered by tests ✅

Comparison is base (8996a74) 99.58% compared to head (1c6d93c) 99.57%.

Additional details and impacted files

@@            Coverage Diff             @@
##             next    #2582      +/-   ##
==========================================
- Coverage   99.58%   99.57%   -0.01%     
==========================================
  Files        2806     2806              
  Lines      250195   250195              
  Branches     1110     1105       -5     
==========================================
- Hits       249151   249144       -7     
- Misses       1016     1023       +7     
  Partials       28       28              

see 2 files 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.