Update HyTTS

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@types/express (source)	4.17.17 -> 4.17.18
@types/jest (source)	29.5.3 -> 29.5.5
@types/lodash (source)	4.14.196 -> 4.14.199
@types/node (source)	18.17.3 -> 18.18.1
@typescript-eslint/eslint-plugin	6.3.0 -> 6.7.3
@typescript-eslint/parser	6.3.0 -> 6.7.3
esbuild	0.19.0 -> 0.19.4
eslint (source)	8.46.0 -> 8.50.0
eslint-import-resolver-typescript	3.5.5 -> 3.6.1
eslint-plugin-import	2.28.0 -> 2.28.1
eslint-plugin-jest	27.2.3 -> 27.4.0
jest (source)	29.6.2 -> 29.7.0
jest-circus	29.6.2 -> 29.7.0
jest-environment-jsdom	29.6.2 -> 29.7.0
prettier (source)	3.0.1 -> 3.0.3
tslib (source)	2.6.1 -> 2.6.2
typescript (source)	5.1.6 -> 5.2.2
zod (source)	3.21.4 -> 3.22.2

---

Release Notes

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

v6.7.3

Compare Source

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

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

v6.7.2

Compare Source

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

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

v6.7.0

Compare Source

Bug Fixes

• eslint-plugin: [no-restricted-imports] disallow side effect imports when allowTypeImports is enabled (#​7560) (4908905)

Features

• eslint-plugin: [await-thenable] added suggestion fixer (#​7437) (b284370)

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

v6.6.0

Compare Source

Bug Fixes

• eslint-plugin: [key-spacing] consider properties with parens and comments (#​7525) (7012279)

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

v6.5.0

Compare Source

Bug Fixes

• eslint-plugin: [consistent-type-assertions] wrap object return value with parentheses (#​6885) (23ac499)

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

6.4.1 (2023-08-21)

Bug Fixes

• eslint-plugin: [no-unnecessary-condition] false positives with branded types (#​7466) (b52658f), closes #​7293

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

v6.4.1

Compare Source

Bug Fixes

• eslint-plugin: [no-unnecessary-condition] false positives with branded types (#​7466) (b52658f), closes #​7293

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

v6.4.0

Compare Source

Bug Fixes

• eslint-plugin: [non-nullable-type-assertion-style] consider operator precedence when fixing (#​7289) (bad37a2)
• eslint-plugin: [strict-boolean-expressions] replace dangerous fixer with suggestions (#​7394) (ad8401a)

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

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

v6.7.3

Compare Source

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

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

v6.7.2

Compare Source

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

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

v6.7.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.6.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.5.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.4.1 (2023-08-21)

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

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

v6.4.1

Compare Source

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

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

v6.4.0

Compare Source

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

Compare Source

• Fix printing of JavaScript decorators in tricky cases (#​3396)

  This release fixes some bugs where esbuild's pretty-printing of JavaScript decorators could incorrectly produced code with a syntax error. The problem happened because esbuild sometimes substitutes identifiers for other expressions in the pretty-printer itself, but the decision about whether to wrap the expression or not didn't account for this. Here are some examples:

  // Original code
  import { constant } from './constants.js'
  import { imported } from 'external'
  import { undef } from './empty.js'
  class Foo {
    @​constant()
    @​imported()
    @​undef()
    foo
  }
  
  // Old output (with --bundle --format=cjs --packages=external --minify-syntax)
  var import_external = require("external");
  var Foo = class {
    @​123()
    @​(0, import_external.imported)()
    @​(void 0)()
    foo;
  };
  
  // New output (with --bundle --format=cjs --packages=external --minify-syntax)
  var import_external = require("external");
  var Foo = class {
    @​(123())
    @​((0, import_external.imported)())
    @​((void 0)())
    foo;
  };

• Allow pre-release versions to be passed to target (#​3388)

  People want to be able to pass version numbers for unreleased versions of node (which have extra stuff after the version numbers) to esbuild's target setting and have esbuild do something reasonable with them. These version strings are of course not present in esbuild's internal feature compatibility table because an unreleased version has not been released yet (by definition). With this release, esbuild will now attempt to accept these version strings passed to target and do something reasonable with them.

v0.19.3

Compare Source

• Fix list-style-type with the local-css loader (#​3325)

  The local-css loader incorrectly treated all identifiers provided to list-style-type as a custom local identifier. That included identifiers such as none which have special meaning in CSS, and which should not be treated as custom local identifiers. This release fixes this bug:

  /* Original code */
  ul { list-style-type: none }
  
  /* Old output (with --loader=local-css) */
  ul {
    list-style-type: stdin_none;
  }
  
  /* New output (with --loader=local-css) */
  ul {
    list-style-type: none;
  }

  Note that this bug only affected code using the local-css loader. It did not affect code using the css loader.

• Avoid inserting temporary variables before use strict (#​3322)

  This release fixes a bug where esbuild could incorrectly insert automatically-generated temporary variables before use strict directives:

  // Original code
  function foo() {
    'use strict'
    a.b?.c()
  }
  
  // Old output (with --target=es6)
  function foo() {
    var _a;
    "use strict";
    (_a = a.b) == null ? void 0 : _a.c();
  }
  
  // New output (with --target=es6)
  function foo() {
    "use strict";
    var _a;
    (_a = a.b) == null ? void 0 : _a.c();
  }

• Adjust TypeScript enum output to better approximate tsc (#​3329)

  TypeScript enum values can be either number literals or string literals. Numbers create a bidirectional mapping between the name and the value but strings only create a unidirectional mapping from the name to the value. When the enum value is neither a number literal nor a string literal, TypeScript and esbuild both default to treating it as a number:

  // Original TypeScript code
  declare const foo: any
  enum Foo {
    NUMBER = 1,
    STRING = 'a',
    OTHER = foo,
  }
  
  // Compiled JavaScript code (from "tsc")
  var Foo;
  (function (Foo) {
    Foo[Foo["NUMBER"] = 1] = "NUMBER";
    Foo["STRING"] = "a";
    Foo[Foo["OTHER"] = foo] = "OTHER";
  })(Foo || (Foo = {}));

  However, TypeScript does constant folding slightly differently than esbuild. For example, it may consider template literals to be string literals in some cases:

  // Original TypeScript code
  declare const foo = 'foo'
  enum Foo {
    PRESENT = `${foo}`,
    MISSING = `${bar}`,
  }
  
  // Compiled JavaScript code (from "tsc")
  var Foo;
  (function (Foo) {
    Foo["PRESENT"] = "foo";
    Foo[Foo["MISSING"] = `${bar}`] = "MISSING";
  })(Foo || (Foo = {}));

  The template literal initializer for PRESENT is treated as a string while the template literal initializer for MISSING is treated as a number. Previously esbuild treated both of these cases as a number but starting with this release, esbuild will now treat both of these cases as a string. This doesn't exactly match the behavior of tsc but in the case where the behavior diverges tsc reports a compile error, so this seems like acceptible behavior for esbuild. Note that handling these cases completely correctly would require esbuild to parse type declarations (see the declare keyword), which esbuild deliberately doesn't do.

• Ignore case in CSS in more places (#​3316)

  This release makes esbuild's CSS support more case-agnostic, which better matches how browsers work. For example:

  /* Original code */
  @​KeyFrames Foo { From { OpaCity: 0 } To { OpaCity: 1 } }
  body { CoLoR: YeLLoW }
  
  /* Old output (with --minify) */
  @​KeyFrames Foo{From {OpaCity: 0} To {OpaCity: 1}}body{CoLoR:YeLLoW}
  
  /* New output (with --minify) */
  @​KeyFrames Foo{0%{OpaCity:0}To{OpaCity:1}}body{CoLoR:#ff0}

  Please never actually write code like this.

• Improve the error message for null entries in exports (#​3377)

  Package authors can disable package export paths with the exports map in package.json. With this release, esbuild now has a clearer error message that points to the null token in package.json itself instead of to the surrounding context. Here is an example of the new error message:

  ✘ [ERROR] Could not resolve "msw/browser"
  
      lib/msw-config.ts:2:28:
        2 │ import { setupWorker } from 'msw/browser';
          ╵                             ~~~~~~~~~~~~~
  
    The path "./browser" cannot be imported from package "msw" because it was explicitly disabled by
    the package author here:
  
      node_modules/msw/package.json:17:14:
        17 │       "node": null,
           ╵               ~~~~
  
    You can mark the path "msw/browser" as external to exclude it from the bundle, which will remove
    this error and leave the unresolved path in the bundle.
  

• Parse and print the with keyword in import statements

  JavaScript was going to have a feature called "import assertions" that adds an assert keyword to import statements. It looked like this:

  import stuff from './stuff.json' assert { type: 'json' }

  The feature provided a way to assert that the imported file is of a certain type (but was not allowed to affect how the import is interpreted, even though that's how everyone expected it to behave). The feature was fully specified and then actually implemented and shipped in Chrome before the people behind the feature realized that they should allow it to affect how the import is interpreted after all. So import assertions are no longer going to be added to the language.

  Instead, the current proposal is to add a feature called "import attributes" instead that adds a with keyword to import statements. It looks like this:

  import stuff from './stuff.json' with { type: 'json' }

  This feature provides a way to affect how the import is interpreted. With this release, esbuild now has preliminary support for parsing and printing this new with keyword. The with keyword is not yet interpreted by esbuild, however, so bundling code with it will generate a build error. All this release does is allow you to use esbuild to process code containing it (such as removing types from TypeScript code). Note that this syntax is not yet a part of JavaScript and may be removed or altered in the future if the specification changes (which it already has once, as described above). If that happens, esbuild reserves the right to remove or alter its support for this syntax too.

v0.19.2

Compare Source

• Update how CSS nesting is parsed again

  CSS nesting syntax has been changed again, and esbuild has been updated to match. Type selectors may now be used with CSS nesting:

  .foo {
    div {
      color: red;
    }
  }

  Previously this was disallowed in the CSS specification because it's ambiguous whether an identifier is a declaration or a nested rule starting with a type selector without requiring unbounded lookahead in the parser. It has now been allowed because the CSS working group has decided that requiring unbounded lookahead is acceptable after all.

  Note that this change means esbuild no longer considers any existing browser to support CSS nesting since none of the existing browsers support this new syntax. CSS nesting will now always be transformed when targeting a browser. This situation will change in the future as browsers add support for this new syntax.

• Fix a scope-related bug with --drop-labels= (#​3311)

  The recently-released --drop-labels= feature previously had a bug where esbuild's internal scope stack wasn't being restored properly when a statement with a label was dropped. This could manifest as a tree-shaking issue, although it's possible that this could have also been causing other subtle problems too. The bug has been fixed in this release.

• Make renamed CSS names unique across entry points (#​3295)

  Previously esbuild's generated names for local names in CSS were only unique within a given entry point (or across all entry points when code splitting was enabled). That meant that building multiple entry points with esbuild could result in local names being renamed to the same identifier even when those entry points were built simultaneously within a single esbuild API call. This problem was especially likely to happen with minification enabled. With this release, esbuild will now avoid renaming local names from two separate entry points to the same name if those entry points were built with a single esbuild API call, even when code splitting is disabled.

• Fix CSS ordering bug with @layer before @import

  CSS lets you put @layer rules before @import rules to define the order of layers in a stylesheet. Previously esbuild's CSS bundler incorrectly ordered these after the imported files because before the introduction of cascade layers to CSS, imported files could be bundled by removing the @import rules and then joining files together in the right order. But with @layer, CSS files may now need to be split apart into multiple pieces in the bundle. For example:

  /* Original code */
  @​layer start;
  @​import "data:text/css,@​layer inner.start;";
  @​import "data:text/css,@​layer inner.end;";
  @​layer end;
  
  /* Old output (with --bundle) */
  @​layer inner.start;
  @​layer inner.end;
  @​layer start;
  @​layer end;
  
  /* New output (with --bundle) */
  @​layer start;
  @​layer inner.start;
  @​layer inner.end;
  @​layer end;
  

• Unwrap nested duplicate @media rules (#​3226)

  With this release, esbuild's CSS minifier will now automatically unwrap duplicate nested @media rules:

  /* Original code */
  @​media (min-width: 1024px) {
    .foo { color: red }
    @​media (min-width: 1024px) {
      .bar { color: blue }
    }
  }
  
  /* Old output (with --minify) */
  @​media (min-width: 1024px){.foo{color:red}@​media (min-width: 1024px){.bar{color:#​00f}}}
  
  /* New output (with --minify) */
  @​media (min-width: 1024px){.foo{color:red}.bar{color:#​00f}}

  These rules are unlikely to be authored manually but may result from using frameworks such as Tailwind to generate CSS.

v0.19.1

Compare Source

• Fix a regression with baseURL in tsconfig.json (#​3307)

  The previous release moved tsconfig.json path resolution before --packages=external checks to allow the paths field in tsconfig.json to avoid a package being marked as external. However, that reordering accidentally broke the behavior of the baseURL field from tsconfig.json. This release moves these path resolution rules around again in an attempt to allow both of these cases to work.

• Parse TypeScript type arguments for JavaScript decorators (#​3308)

  When parsing JavaScript decorators in TypeScript (i.e. with experimentalDecorators disabled), esbuild previously didn't parse type arguments. Type arguments will now be parsed starting with this release. For example:

  @&#8203;foo<number>
  @&#8203;bar<number, string>()
  class Foo {}

• Fix glob patterns matching extra stuff at the end (#​3306)

  Previously glob patterns such as ./*.js would incorrectly behave like ./*.js* during path matching (also matching .js.map files, for example). This was never intentional behavior, and has now been fixed.

• Change the permissions of esbuild's generated output files (#​3285)

  This release changes the permissions of the output files that esbuild generates to align with the default behavior of node's fs.writeFileSync function. Since most tools written in JavaScript use fs.writeFileSync, this should make esbuild more consistent with how other JavaScript build tools behave.

  The full Unix-y details: Unix permissions use three-digit octal notation where the three digits mean "user, group, other" in that order. Within a digit, 4 means "read" and 2 means "write" and 1 means "execute". So 6 == 4 + 2 == read + write. Previously esbuild uses 0644 permissions (the leading 0 means octal notation) but the permissions for fs.writeFileSync defaults to 0666, so esbuild will now use 0666 permissions. This does not necessarily mean that the files esbuild generates will end up having 0666 permissions, however, as there is another Unix feature called "umask" where the operating system masks out some of these bits. If your umask is set to 0022 then the generated files will have 0644 permissions, and if your umask is set to 0002 then the generated files will have 0664 permissions.

• Fix a subtle CSS ordering issue with @import and @layer

  With this release, esbuild may now introduce additional @layer rules when bundling CSS to better preserve the layer ordering of the input code. Here's an example of an edge case where this matters:

  /* entry.css */
  @​import "a.css";
  @​import "b.css";
  @​import "a.css";

  /* a.css */
  @​layer a {
    body {
      background: red;
    }
  }

  /* b.css */
  @​layer b {
    body {
      background: green;
    }
  }

  This CSS should set the body background to green, which is what happens in the browser. Previously esbuild generated the following output which incorrectly sets the body background to red:

  /* b.css */
  @​layer b {
    body {
      background: green;
    }
  }
  
  /* a.css */
  @​layer a {
    body {
      background: red;
    }
  }

  This difference in behavior is because the browser evaluates a.css + b.css + a.css (in CSS, each @import is replaced with a copy of the imported file) while esbuild was only writing out b.css + a.css. The first copy of a.css wasn't being written out by esbuild for two reasons: 1) bundlers care about code size and try to avoid emitting duplicate CSS and 2) when there are multiple copies of a CSS file, normally only the last copy matters since the last declaration with equal specificity wins in CSS.

  However, @layer was recently added to CSS and for @layer the first copy matters because layers are ordered using their first location in source code order. This introduction of @layer means esbuild needs to change its bundling algorithm. An easy solution would be for esbuild to write out a.css twice, but that would be inefficient. So what I'm going to try to have esbuild do with this release is to write out an abbreviated form of the first copy of a CSS file that only includes the @layer information, and then still only write out the full CSS file once for the last copy. So esbuild's output for this edge case now looks like this:

  /* a.css */
  @​layer a;
  
  /* b.css */
  @​layer b {
    body {
      background: green;
    }
  }
  
  /* a.css */
  @​layer a {
    body {
      background: red;
    }
  }

  The behavior of the bundled CSS now matches the behavior of the unbundled CSS. You may be wondering why esbuild doesn't just write out a.css first followed by b.css. That would work in this case but it doesn't work in general because for any rules outside of a @layer rule, the last copy should still win instead of the first copy.

• Fix a bug with esbuild's TypeScript type definitions (#​3299)

  This release fixes a copy/paste error with the TypeScript type definitions for esbuild's JS API:

   export interface TsconfigRaw {
     compilerOptions?: {
  -    baseUrl?: boolean
  +    baseUrl?: string
       ...
     }
   }

  This fix was contributed by @​privatenumber.

eslint/eslint (eslint)

v8.50.0

Compare Source

Features

• 27d5a9e feat: add suggestions to array-callback-return (#​17590) (Tanuj Kanti)
• f9082ff feat: flat-rule-tester make sure default config always matches (#​17585) (fnx)
• 83914ad feat: Implement SourceCode#applyInlineConfig() (#​17351) (Nicholas C. Zakas)
• 22a5582 feat: add rule no-object-constructor, deprecate no-new-object (#​17576) (Francesco Trotta)
• 85a3d9e feat: allowVoid option in array-callback-return (#​17564) (Tanuj Kanti)

Bug Fixes

• cc4d26b fix: Ensure deprecated context.parserServices warns (#​17593) (Nicholas C. Zakas)
• 1ea4cfb fix: Ensure all RuleTester tests all deprecated context methods (#​17587) (Nicholas C. Zakas)
• aa1b657 fix: wrong suggestion and message in no-misleading-character-class (#​17571) (Yosuke Ota)

Documentation

• 1800537 docs: Fix and standardize JSX code examples (#​17591) (Francesco Trotta)
• 48a44a7 docs: Add correct/incorrect tags to prefer-arrow-callback (#​17589) (Francesco Trotta)
• 20893d4 docs: fix incorrect tag's place (#​17575) (Tanuj Kanti)
• bd7a71f docs: Update README (GitHub Actions Bot)

Chores

• f8a8a2d chore: upgrade @​eslint/js@​8.50.0 (#​17599) (Milos Djermanovic)
• 38ada6d chore: package.json update for @​eslint/js release (ESLint Jenkins)

v8.49.0

Compare Source

Features

• da09f4e feat: Implement onUnreachableCodePathStart/End (#​17511) (Nicholas C. Zakas)
• 32b2327 feat: Emit deprecation warnings in RuleTester (#​17527) (Nicholas C. Zakas)
• acb7df3 feat: add new enforce option to lines-between-class-members (#​17462) (Nitin Kumar)

Documentation

• ecfb54f docs: Update README (GitHub Actions Bot)
• de86b3b docs: update no-promise-executor-return examples (#​17529) (Nitin Kumar)
• 032c4b1 docs: add typescript template (#​17500) (James)
• cd7da5c docs: Update README (GitHub Actions Bot)

Chores

• b7621c3 chore: remove browser test from npm test (#​17550) (Milos Djermanovic)
• cac45d0 chore: upgrade @​eslint/js@​8.49.0 (#​17549) (Milos Djermanovic)
• cd39508 chore: package.json update for @​eslint/js release (ESLint Jenkins)
• 203a971 ci: bump actions/checkout from 3 to 4 (#​17530) (dependabot[bot])
• a40fa50 chore: use eslint-plugin-jsdoc's flat config (#​17516) (Milos Djermanovic)
• 926a286 test: replace Karma with Webdriver.IO (#​17126) (Christian Bromann)
• f591d2c chore: Upgrade config-array (#​17512) (Nicholas C. Zakas)

v8.48.0

Compare Source

Features

• 1fbb3b0 feat: correct update direction in for-direction (#​17483) (Francesco Trotta)
• d73fbf2 feat: rule tester do not create empty valid or invalid test suites (#​17475) (fnx)
• ee2f718 feat: Allow void in rule no-promise-executor-return (#​17282) (nopeless)

Bug Fixes

• 7234f6a fix: update RuleTester JSDoc and deprecations (#​17496) (Jonas Berlin)

Documentation

• 7a51d77 docs: no-param-reassign mention strict mode (#​17494) (Stephen Hardy)
• 9cd7ac2 docs: add fetch script to package.json conventions (#​17459) (Nitin Kumar)
• cab21e6 docs: advice for inline disabling of rules (#​17458) (Ashish Yadav)
• 056499d docs: fix example of flat config from plugin (#​17482) (Francesco Trotta)
• 9e9edf9 docs: update documentation URL in error message (#​17465) (Nitin Kumar)

Chores

• 8dd3cec chore: upgrade @​eslint/js@​8.48.0 (#​17501) (Milos Djermanovic)
• 6d0496e chore: package.json update for @​eslint/js release (ESLint Jenkins)
• 9d4216d chore: Refactor and document CodePathSegment (#​17474) (Nicholas C. Zakas)

v8.47.0

Compare Source

Features

• 53d7508 feat: update regex for methods with thisArg (#​17439) (Francesco Trotta)

Bug Fixes

• 631648e fix: do not report on shadowed constructors in no-new-wrappers (#​17447) (Francesco Trotta)

Documentation

• a766a48 docs: document lack of config file names (#​17442) (James)
• a1635d6 docs: Update README (GitHub Actions Bot)
• 47a0859 docs: update require-unicode-regexp.md as following up #​17402 (#​17441) (SUZUKI Sosuke)
• fcdc85d docs: Update README (GitHub Actions Bot)
• 2a92b6c docs: update with "Specifying Parser Options" (#​17435) (Cheol-Won)
• d743ed3 docs: add metadata for parser/processor (#​17438) (Huáng Jùnliàng)
• 224376c docs: Update README (GitHub Actions Bot)
• a41a8e4 docs: update script names in README (#​17432) (Nitin Kumar)

Chores

• bf69aa6 chore: Update dependencies (#​17456) (Nicholas C. Zakas)
• 0e45760 chore: package.json update for @​eslint/js release (ESLint Jenkins)
• 757bfe1 chore: Remove add-to-triage (#​17450) (Nicholas C. Zakas)
• b066640 chore: standardize npm script names (#​17431) (Nitin Kumar)
• 6b2410f chore: Update add-to-triage.yml (#​17444) (Nicholas C. Zakas)

import-js/eslint-import-resolver-typescript (eslint-import-resolver-typescript)

v3.6.1

Compare Source

Patch Changes

• #​241 cf5d67f Thanks @​klippx! - Fix CJS import to make it compatible with ESM projects

v3.6.0

---

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.