chore(deps): update all non-major dependencies

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@types/node (source)	18.11.13 -> 18.11.17
@typescript-eslint/eslint-plugin	5.46.0 -> 5.46.1
@typescript-eslint/parser	5.46.0 -> 5.46.1
esbuild	0.16.4 -> 0.16.9
eslint (source)	8.29.0 -> 8.30.0
pino (source)	8.7.0 -> 8.8.0
vitest	0.25.7 -> 0.25.8

---

Release Notes

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

v5.46.1

Compare Source

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

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

v5.46.1

Compare Source

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

evanw/esbuild

v0.16.9

Compare Source

• Update to Unicode 15.0.0

  The character tables that determine which characters form valid JavaScript identifiers have been updated from Unicode version 14.0.0 to the newly-released Unicode version 15.0.0. I'm not putting an example in the release notes because all of the new characters will likely just show up as little squares since fonts haven't been updated yet. But you can read https://www.unicode.org/versions/Unicode15.0.0/#Summary for more information about the changes.

• Disallow duplicate lexically-declared names in nested blocks and in strict mode

  In strict mode or in a nested block, it's supposed to be a syntax error to declare two symbols with the same name unless all duplicate entries are either function declarations or all var declarations. However, esbuild was overly permissive and allowed this when duplicate entries were either function declarations or var declarations (even if they were mixed). This check has now been made more restrictive to match the JavaScript specification:

  // JavaScript allows this
  var a
  function a() {}
  {
    var b
    var b
    function c() {}
    function c() {}
  }
  
  // JavaScript doesn't allow this
  {
    var d
    function d() {}
  }

• Add a type declaration for the new empty loader (#​2755)

  I forgot to add this in the previous release. It has now been added.

  This fix was contributed by @​fz6m.

• Add support for the v flag in regular expression literals

  People are currently working on adding a v flag to JavaScript regular expresions. You can read more about this flag here: https://v8.dev/features/regexp-v-flag. This release adds support for parsing this flag, so esbuild will now no longer consider regular expression literals with this flag to be a syntax error. If the target is set to something other than esnext, esbuild will transform regular expression literals containing this flag into a new RegExp() constructor call so the resulting code doesn't have a syntax error. This enables you to provide a polyfill for RegExp that implements the v flag to get your code to work at run-time. While esbuild doesn't typically adopt proposals until they're already shipping in a real JavaScript run-time, I'm adding it now because a) esbuild's implementation doesn't need to change as the proposal evolves, b) this isn't really new syntax since regular expression literals already have flags, and c) esbuild's implementation is a trivial pass-through anyway.

• Avoid keeping the name of classes with static name properties

  The --keep-names property attempts to preserve the original value of the name property for functions and classes even when identifiers are renamed by the minifier or to avoid a name collision. This is currently done by generating code to assign a string to the name property on the function or class object. However, this should not be done for classes with a static name property since in that case the explicitly-defined name property overwrites the automatically-generated class name. With this release, esbuild will now no longer attempt to preserve the name property for classes with a static name property.

v0.16.8

Compare Source

• Allow plugins to resolve injected files (#​2754)

  Previously paths passed to the inject feature were always interpreted as file system paths. This meant that onResolve plugins would not be run for them and esbuild's default path resolver would always be used. This meant that the inject feature couldn't be used in the browser since the browser doesn't have access to a file system. This release runs paths passed to inject through esbuild's full path resolution pipeline so plugins now have a chance to handle them using onResolve callbacks. This makes it possible to write a plugin that makes esbuild's inject work in the browser.

• Add the empty loader (#​1541, #​2753)

  The new empty loader tells esbuild to pretend that a file is empty. So for example --loader:.css=empty effectively skips all imports of .css files in JavaScript so that they aren't included in the bundle, since import "./some-empty-file" in JavaScript doesn't bundle anything. You can also use the empty loader to remove asset references in CSS files. For example --loader:.png=empty causes esbuild to replace asset references such as url(image.png) with url() so that they are no longer included in the resulting style sheet.

• Fix </script> and </style> escaping for non-default targets (#​2748)

  The change in version 0.16.0 to give control over </script> escaping via --supported:inline-script=false or --supported:inline-script=true accidentally broke automatic escaping of </script> when an explicit target setting is specified. This release restores the correct automatic escaping of </script> (which should not depend on what target is set to).

• Enable the exports field with NODE_PATHS (#​2752)

  Node has a rarely-used feature where you can extend the set of directories that node searches for packages using the NODE_PATHS environment variable. While esbuild supports this too, previously it only supported the old main field path resolution but did not support the new exports field package resolution. This release makes the path resolution rules the same again for both node_modules directories and NODE_PATHS directories.

v0.16.7

Compare Source

• Include file loader strings in metafile imports (#​2731)

  Bundling a file with the file loader copies that file to the output directory and imports a module with the path to the copied file in the default export. Previously when bundling with the file loader, there was no reference in the metafile from the JavaScript file containing the path string to the copied file. With this release, there will now be a reference in the metafile in the imports array with the kind file-loader:

   {
     ...
     "outputs": {
       "out/image-55CCFTCE.svg": {
         ...
       },
       "out/entry.js": {
         "imports": [
  +        {
  +          "path": "out/image-55CCFTCE.svg",
  +          "kind": "file-loader"
  +        }
         ],
         ...
       }
     }
   }

• Fix byte counts in metafile regarding references to other output files (#​2071)

  Previously files that contained references to other output files had slightly incorrect metadata for the byte counts of input files which contributed to that output file. So for example if app.js imports image.png using the file loader and esbuild generates out.js and image-LSAMBFUD.png, the metadata for how many bytes of out.js are from app.js was slightly off (the metadata for the byte count of out.js was still correct). The reason is because esbuild substitutes the final paths for references between output files toward the end of the build to handle cyclic references, and the byte counts needed to be adjusted as well during the path substitution. This release fixes these byte counts (specifically the bytesInOutput values).

• The alias feature now strips a trailing slash (#​2730)

  People sometimes add a trailing slash to the name of one of node's built-in modules to force node to import from the file system instead of importing the built-in module. For example, importing util imports node's built-in module called util but importing util/ tries to find a package called util on the file system. Previously attempting to use esbuild's package alias feature to replace imports to util with a specific file would fail because the file path would also gain a trailing slash (e.g. mapping util to ./file.js turned util/ into ./file.js/). With this release, esbuild will now omit the path suffix if it's a single trailing slash, which should now allow you to successfully apply aliases to these import paths.

v0.16.6

Compare Source

• Do not mark subpath imports as external with --packages=external (#​2741)

  Node has a feature called subpath imports where special import paths that start with # are resolved using the imports field in the package.json file of the enclosing package. The intent of the newly-added --packages=external setting is to exclude a package's dependencies from the bundle. Since a package's subpath imports are only accessible within that package, it's wrong for them to be affected by --packages=external. This release changes esbuild so that --packages=external no longer affects subpath imports.

• Forbid invalid numbers in JSON files

  Previously esbuild parsed numbers in JSON files using the same syntax as JavaScript. But starting from this release, esbuild will now parse them with JSON syntax instead. This means the following numbers are no longer allowed by esbuild in JSON files:

  • Legacy octal literals (non-zero integers starting with 0)
  • The 0b, 0o, and 0x numeric prefixes
  • Numbers containing _ such as 1_000
  • Leading and trailing . such as 0. and .0
  • Numbers with a space after the - such as - 1

• Add external imports to metafile (#​905, #​1768, #​1933, #​1939)

  External imports now appear in imports arrays in the metafile (which is present when bundling with metafile: true) next to normal imports, but additionally have external: true to set them apart. This applies both to files in the inputs section and the outputs section. Here's an example:

   {
     "inputs": {
       "style.css": {
         "bytes": 83,
         "imports": [
  +        {
  +          "path": "https://cdn.jsdelivr.net/npm/bootstrap@5.2.3/dist/css/bootstrap.min.css",
  +          "kind": "import-rule",
  +          "external": true
  +        }
         ]
       },
       "app.js": {
         "bytes": 100,
         "imports": [
  +        {
  +          "path": "https://cdn.jsdelivr.net/npm/bootstrap@5.2.3/dist/js/bootstrap.min.js",
  +          "kind": "import-statement",
  +          "external": true
  +        },
           {
             "path": "style.css",
             "kind": "import-statement"
           }
         ]
       }
     },
     "outputs": {
       "out/app.js": {
         "imports": [
  +        {
  +          "path": "https://cdn.jsdelivr.net/npm/bootstrap@5.2.3/dist/js/bootstrap.min.js",
  +          "kind": "require-call",
  +          "external": true
  +        }
         ],
         "exports": [],
         "entryPoint": "app.js",
         "cssBundle": "out/app.css",
         "inputs": {
           "app.js": {
             "bytesInOutput": 113
           },
           "style.css": {
             "bytesInOutput": 0
           }
         },
         "bytes": 528
       },
       "out/app.css": {
         "imports": [
  +        {
  +          "path": "https://cdn.jsdelivr.net/npm/bootstrap@5.2.3/dist/css/bootstrap.min.css",
  +          "kind": "import-rule",
  +          "external": true
  +        }
         ],
         "inputs": {
           "style.css": {
             "bytesInOutput": 0
           }
         },
         "bytes": 100
       }
     }
   }

  One additional useful consequence of this is that the imports array is now populated when bundling is disabled. So you can now use esbuild with bundling disabled to inspect a file's imports.

v0.16.5

Compare Source

• Make it easy to exclude all packages from a bundle (#​1958, #​1975, #​2164, #​2246, #​2542)

  When bundling for node, it's often necessary to exclude npm packages from the bundle since they weren't designed with esbuild bundling in mind and don't work correctly after being bundled. For example, they may use __dirname and run-time file system calls to load files, which doesn't work after bundling with esbuild. Or they may compile a native .node extension that has similar expectations about the layout of the file system that are no longer true after bundling (even if the .node extension is copied next to the bundle).

  The way to get this to work with esbuild is to use the --external: flag. For example, the fsevents package contains a native .node extension and shouldn't be bundled. To bundle code that uses it, you can pass --external:fsevents to esbuild to exclude it from your bundle. You will then need to ensure that the fsevents package is still present when you run your bundle (e.g. by publishing your bundle to npm as a package with a dependency on fsevents).

  It was possible to automatically do this for all of your dependencies, but it was inconvenient. You had to write some code that read your package.json file and passed the keys of the dependencies, devDependencies, peerDependencies, and/or optionalDependencies maps to esbuild as external packages (either that or write a plugin to mark all package paths as external). Previously esbuild's recommendation for making this easier was to do --external:./node_modules/* (added in version 0.14.13). However, this was a bad idea because it caused compatibility problems with many node packages as it caused esbuild to mark the post-resolve path as external instead of the pre-resolve path. Doing that could break packages that are published as both CommonJS and ESM if esbuild's bundler is also used to do a module format conversion.

  With this release, you can now do the following to automatically exclude all packages from your bundle:

  • CLI:

    esbuild --bundle --packages=external
    

  • JS:

    esbuild.build({
      bundle: true,
      packages: 'external',
    })

  • Go:

    api.Build(api.BuildOptions{
      Bundle:   true,
      Packages: api.PackagesExternal,
    })

  Doing --external:./node_modules/* is still possible and still has the same behavior, but is no longer recommended. I recommend that you use the new packages feature instead.

• Fix some subtle bugs with tagged template literals

  This release fixes a bug where minification could incorrectly change the value of this within tagged template literal function calls:

  // Original code
  function f(x) {
    let z = y.z
    return z``
  }
  
  // Old output (with --minify)
  function f(n){return y.z``}
  
  // New output (with --minify)
  function f(n){return(0,y.z)``}

  This release also fixes a bug where using optional chaining with --target=es2019 or earlier could incorrectly change the value of this within tagged template literal function calls:

  // Original code
  var obj = {
    foo: function() {
      console.log(this === obj);
    }
  };
  (obj?.foo)``;
  
  // Old output (with --target=es6)
  var obj = {
    foo: function() {
      console.log(this === obj);
    }
  };
  (obj == null ? void 0 : obj.foo)``;
  
  // New output (with --target=es6)
  var __freeze = Object.freeze;
  var __defProp = Object.defineProperty;
  var __template = (cooked, raw) => __freeze(__defProp(cooked, "raw", { value: __freeze(raw || cooked.slice()) }));
  var _a;
  var obj = {
    foo: function() {
      console.log(this === obj);
    }
  };
  (obj == null ? void 0 : obj.foo).call(obj, _a || (_a = __template([""])));

• Some slight minification improvements

  The following minification improvements were implemented:

  • if (~a !== 0) throw x; => if (~a) throw x;
  • if ((a | b) !== 0) throw x; => if (a | b) throw x;
  • if ((a & b) !== 0) throw x; => if (a & b) throw x;
  • if ((a ^ b) !== 0) throw x; => if (a ^ b) throw x;
  • if ((a << b) !== 0) throw x; => if (a << b) throw x;
  • if ((a >> b) !== 0) throw x; => if (a >> b) throw x;
  • if ((a >>> b) !== 0) throw x; => if (a >>> b) throw x;
  • if (!!a || !!b) throw x; => if (a || b) throw x;
  • if (!!a && !!b) throw x; => if (a && b) throw x;
  • if (a ? !!b : !!c) throw x; => if (a ? b : c) throw x;

eslint/eslint

v8.30.0

Compare Source

Features

• 075ef2c feat: add suggestion for no-return-await (#​16637) (Daniel Bartholomae)
• 7190d98 feat: update globals (#​16654) (Sébastien Règne)

Bug Fixes

• 1a327aa fix: Ensure flat config unignores work consistently like eslintrc (#​16579) (Nicholas C. Zakas)
• 9b8bb72 fix: autofix recursive functions in no-var (#​16611) (Milos Djermanovic)

Documentation

• 6a8cd94 docs: Clarify Discord info in issue template config (#​16663) (Nicholas C. Zakas)
• ad44344 docs: CLI documentation standardization (#​16563) (Ben Perlmutter)
• 293573e docs: fix broken line numbers (#​16606) (Sam Chen)
• fa2c64b docs: use relative links for internal links (#​16631) (Percy Ma)
• 75276c9 docs: reorder options in no-unused-vars (#​16625) (Milos Djermanovic)
• 7276fe5 docs: Fix anchor in URL (#​16628) (Karl Horky)
• 6bef135 docs: don't apply layouts to html formatter example (#​16591) (Tanuj Kanti)
• dfc7ec1 docs: Formatters page updates (#​16566) (Ben Perlmutter)
• 8ba124c docs: update the prefer-const example (#​16607) (Pavel)
• e6cb05a docs: fix css leaking (#​16603) (Sam Chen)

Chores

• f2c4737 chore: upgrade @​eslint/eslintrc@​1.4.0 (#​16675) (Milos Djermanovic)
• ba74253 chore: standardize npm script names per #​14827 (#​16315) (Patrick McElhaney)
• 0d9af4c ci: fix npm v9 problem with file: (#​16664) (Milos Djermanovic)
• 90c9219 refactor: migrate off deprecated function-style rules in all tests (#​16618) (Bryan Mishkin)

pinojs/pino

v8.8.0

Compare Source

What's Changed

• Update async logging caveats documentation by @​jonathansamines in https://github.com/pinojs/pino/pull/1578
• Update hapi-pino usage example by @​jonathansamines in https://github.com/pinojs/pino/pull/1580
• build(deps): bump pnpm/action-setup from 2.2.2 to 2.2.4 by @​dependabot in https://github.com/pinojs/pino/pull/1582
• Use safe stringify for redaction by @​bbi22 in https://github.com/pinojs/pino/pull/1587
• Fix updating errorKey with default error serializer (#​1593) by @​zahar517 in https://github.com/pinojs/pino/pull/1604

New Contributors

• @​jonathansamines made their first contribution in https://github.com/pinojs/pino/pull/1578
• @​bbi22 made their first contribution in https://github.com/pinojs/pino/pull/1587
• @​zahar517 made their first contribution in https://github.com/pinojs/pino/pull/1604

Full Changelog: pinojs/pino@v8.7.0...v8.8.0

vitest-dev/vitest

v0.25.8

Compare Source

   🚀 Features

• Add mts, cts files to coverage  -  by @​poyoho and @​AriPerkkio in https://github.com/vitest-dev/vitest/issues/2492 (799f9)

   🐞 Bug Fixes

• Don't throw unhandled error, if import was caught  -  by @​sheremet-va in https://github.com/vitest-dev/vitest/issues/2494 (0a87e)
• coverage: Esbuild to preserve legal comments for ignore hints  -  by @​AriPerkkio in https://github.com/vitest-dev/vitest/issues/2496 (c85ed)

    View changes on GitHub

---

Configuration

📅 Schedule: Branch creation - "before 3am on Monday" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

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