chore(deps): update all non-major dependencies #128

renovate · 2024-01-08T01:51:51Z

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@types/node (source)	`20.10.4` -> `20.10.7`
@typescript-eslint/eslint-plugin (source)	`6.13.2` -> `6.18.0`
@typescript-eslint/parser (source)	`6.13.2` -> `6.18.0`
esbuild	`0.19.9` -> `0.19.11`
eslint (source)	`8.55.0` -> `8.56.0`
eslint-plugin-prettier	`5.0.1` -> `5.1.2`
pino (source)	`8.16.2` -> `8.17.2`
pino-pretty	`10.2.3` -> `10.3.1`
tsx	`4.6.2` -> `4.7.0`
vitest (source)	`1.0.4` -> `1.1.3`

Release Notes

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

`v6.18.0`

Compare Source

🚀 Features

typescript-estree: throw on invalid update expressions
eslint-plugin: [no-var-requires, no-require-imports] allow option

❤️ Thank You

auvred
Joshua Chen

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

`v6.17.0`

Compare Source

Bug Fixes

eslint-plugin: [no-restricted-imports] prevent crash when patterns or paths in options are empty (#8108) (675e987)

Features

eslint-plugin: [no-floating-promises] flag result of .map(async) (#7897) (5857356)
eslint-plugin: [switch-exhaustiveness-check] add an option to warn against a default case on an already exhaustive switch (#7539) (6a219bd)

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

`v6.16.0`

Compare Source

Bug Fixes

eslint-plugin: [unbound-method] exempt all non-Promise built-in statics (#8096) (3182959)

Features

eslint-plugin: deprecate formatting (meta.type: layout) rules (#8073) (04dea84)
eslint-plugin: deprecate no-extra-semi in favor of ESLint Stylistic equivalent (#8123) (9368bf3)

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

`v6.15.0`

Compare Source

Features

eslint-plugin: [no-useless-template-literals] add new rule (#7957) (ff75785), closes #2846
require-array-sort-compare + toSorted (#8052) (c9661c8)

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

`v6.14.0`

Compare Source

Bug Fixes

eslint-plugin: add no-unsafe-unary-minus, prefer-destructuring to disable-type-checked (#8038) (431cd15)
eslint-plugin: correct message for no-unsafe-unary-minus (#7998) (705370a)

Features

eslint-plugin: [explicit-function-return-type] add support for typed class property definitions (#8027) (bff47d7)
eslint-plugin: [require-await] allow yielding Promise in async generators (#8003) (4c3e704)

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

6.13.2 (2023-12-04)

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

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

6.13.1 (2023-11-28)

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

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

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

`v6.18.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.

`v6.17.0`

Compare Source

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

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

`v6.16.0`

Compare Source

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

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

`v6.15.0`

Compare Source

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

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

`v6.14.0`

Compare Source

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

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

6.13.2 (2023-12-04)

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

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

6.13.1 (2023-11-28)

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

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

evanw/esbuild (esbuild)

`v0.19.11`

Compare Source

Fix TypeScript-specific class transform edge case (#3559)

The previous release introduced an optimization that avoided transforming super() in the class constructor for TypeScript code compiled with useDefineForClassFields set to false if all class instance fields have no initializers. The rationale was that in this case, all class instance fields are omitted in the output so no changes to the constructor are needed. However, if all of this is the case and there are #private instance fields with initializers, those private instance field initializers were still being moved into the constructor. This was problematic because they were being inserted before the call to super() (since super() is now no longer transformed in that case). This release introduces an additional optimization that avoids moving the private instance field initializers into the constructor in this edge case, which generates smaller code, matches the TypeScript compiler's output more closely, and avoids this bug:
```
// Original code
class Foo extends Bar {
  #private = 1;
  public: any;
  constructor() {
    super();
  }
}

// Old output (with esbuild v0.19.9)
class Foo extends Bar {
  constructor() {
    super();
    this.#private = 1;
  }
  #private;
}

// Old output (with esbuild v0.19.10)
class Foo extends Bar {
  constructor() {
    this.#private = 1;
    super();
  }
  #private;
}

// New output
class Foo extends Bar {
  #private = 1;
  constructor() {
    super();
  }
}
```

Minifier: allow reording a primitive past a side-effect (#3568)

The minifier previously allowed reordering a side-effect past a primitive, but didn't handle the case of reordering a primitive past a side-effect. This additional case is now handled:

// Original code
function f() {
  let x = false;
  let y = x;
  const boolean = y;
  let frag = $.template(`<p contenteditable="${boolean}">hello world</p>`);
  return frag;
}

// Old output (with --minify)
function f(){const e=!1;return $.template(`<p contenteditable="${e}">hello world</p>`)}

// New output (with --minify)
function f(){return $.template('<p contenteditable="false">hello world</p>')}

Minifier: consider properties named using known Symbol instances to be side-effect free (#3561)

Many things in JavaScript can have side effects including property accesses and ToString operations, so using a symbol such as Symbol.iterator as a computed property name is not obviously side-effect free. This release adds a special case for known Symbol instances so that they are considered side-effect free when used as property names. For example, this class declaration will now be considered side-effect free:
```
class Foo {
  *[Symbol.iterator]() {
  }
}
```
Provide the stop() API in node to exit esbuild's child process (#3558)

You can now call stop() in esbuild's node API to exit esbuild's child process to reclaim the resources used. It only makes sense to do this for a long-lived node process when you know you will no longer be making any more esbuild API calls. It is not necessary to call this to allow node to exit, and it's advantageous to not call this in between calls to esbuild's API as sharing a single long-lived esbuild child process is more efficient than re-creating a new esbuild child process for every API call. This API call used to exist but was removed in version 0.9.0. This release adds it back due to a user request.

`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 = /* @&#8203;__NO_SIDE_EFFECTS__ */ (a, ...b) => ({ a, b })
html`<a>remove</a>`
x = html`keep`

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

// New output (with --tree-shaking=true)
const html = /* @&#8203;__NO_SIDE_EFFECTS__ */ (a, ...b) => ({ a, b });
x = html`keep`;
```
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)

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

`v5.1.2`

Compare Source

Patch Changes

#623 8210e44 Thanks @BPScott! - Add exports mapping to package.json, to allow import eslintPluginRecommended from 'eslint-plugin-prettier/recommended' to work as expected.

Strictly speaking this is a breaking change as it removes the ability for people to import from "eslint-plugin-prettier/eslint-plugin-prettier.js" and "eslint-plugin-prettier/recommended.js" but the former was never recommended in the first place and the latter has only been available for a few days.
#621 2b09e7f Thanks @JounQin! - feat: support parsing markdown via eslint-mdx natively

`v5.1.1`

Compare Source

Patch Changes

#619 b5c0dc5 Thanks @JounQin! - chore: skip formatting inline scripts in pug files

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