fix(deps): update npm - - package.json #883

renovate · 2025-01-27T13:27:07Z

This PR contains the following updates:

Package	Change	Age	Confidence
@babel/core (source)	`^7.27.1` -> `^7.28.0`
@babel/eslint-parser (source)	`^7.27.1` -> `^7.28.0`
@commitlint/cli (source)	`^19.0.0` -> `^19.8.1`
@commitlint/config-conventional (source)	`^19.0.0` -> `^19.8.1`
@esbuild/darwin-arm64	`^0.25.6` -> `^0.25.8`
@esbuild/darwin-x64	`^0.25.6` -> `^0.25.8`
@esbuild/linux-x64	`0.25.6` -> `0.25.8`
@esbuild/win32-x64	`0.25.6` -> `0.25.8`
@material-ui/core (source)	`^4.11.0` -> `^4.12.4`
@primer/octicons-react (source)	`^19.8.0` -> `^19.15.5`
@seald-io/nedb	`^4.0.2` -> `^4.1.2`
@types/express (source)	`^5.0.1` -> `^5.0.3`
@types/express-http-proxy (source)	`^1.6.6` -> `^1.6.7`
@types/lodash (source)	`^4.17.15` -> `^4.17.20`
@types/node (source)	`^22.13.5` -> `^22.17.0`
@types/react-dom (source)	`^17.0.11` -> `^17.0.26`
@typescript-eslint/eslint-plugin (source)	`^8.29.0` -> `^8.38.0`
@typescript-eslint/parser (source)	`^8.29.0` -> `^8.38.0`
@vitejs/plugin-react (source)	`^4.0.2` -> `^4.7.0`
axios (source)	`^1.6.0` -> `^1.11.0`
chai (source)	`^4.2.0` -> `^4.5.0`
chai-http	`^4.3.0` -> `^4.4.0`
concurrently	`^9.0.0` -> `^9.2.0`
cypress (source)	`^14.5.1` -> `^14.5.3`
diff2html (source)	`^3.4.33` -> `^3.4.52`
eslint (source)	`^8.57.0` -> `^8.57.1`
eslint-config-prettier	`^10.0.1` -> `^10.1.8`
eslint-plugin-prettier	`^5.0.0` -> `^5.5.3`
eslint-plugin-react	`^7.21.5` -> `^7.37.5`
express-http-proxy	`^2.0.0` -> `^2.1.1`
express-rate-limit	`^7.1.5` -> `^7.5.1`
express-session	`^1.17.1` -> `^1.18.2`
husky	`^9.0.0` -> `^9.1.7`
isomorphic-git (source)	`^1.27.1` -> `^1.32.2`
jsonschema	`^1.4.1` -> `^1.5.0`
load-plugin	`^6.0.0` -> `^6.0.3`
moment (source)	`^2.29.4` -> `^2.30.1`
mongodb	`^5.0.0` -> `^5.9.2`
nodemailer (source)	`^6.6.1` -> `^6.10.1`
openid-client	`^6.4.2` -> `^6.6.2`
passport-activedirectory	`^1.0.4` -> `^1.4.0`
perfect-scrollbar (source)	`^1.5.5` -> `^1.5.6`
prettier (source)	`^3.0.0` -> `^3.6.2`
react (source)	`^16.13.1` -> `^16.14.0`
react-dom (source)	`^16.13.1` -> `^16.14.0`
react-router-dom (source)	`6.28.2` -> `6.30.1`
simple-git (source)	`^3.25.0` -> `^3.28.0`
tsx (source)	`^4.19.3` -> `^4.20.3`
typescript (source)	`^5.7.3` -> `^5.8.3`
uuid	`^11.0.0` -> `^11.1.0`

Release Notes

conventional-changelog/commitlint (@commitlint/cli)

`v19.8.1`

Compare Source

Bug Fixes

update dependency tinyexec to v1 (#4332) (e49449f)

`v19.8.0`

Compare Source

Performance Improvements

use node: prefix to bypass require.cache call for builtins (#4302) (0cd8f41)

19.7.1 (2025-02-02)

Note: Version bump only for package @commitlint/cli

19.6.1 (2024-12-15)

Note: Version bump only for package @commitlint/cli

`v19.7.1`

Compare Source

Note: Version bump only for package @commitlint/cli

conventional-changelog/commitlint (@commitlint/config-conventional)

`v19.8.1`

Compare Source

Note: Version bump only for package @commitlint/config-conventional

`v19.8.0`

Compare Source

Performance Improvements

use node: prefix to bypass require.cache call for builtins (#4302) (0cd8f41)

19.7.1 (2025-02-02)

Note: Version bump only for package @commitlint/config-conventional

`v19.7.1`

Compare Source

Note: Version bump only for package @commitlint/config-conventional

evanw/esbuild (@esbuild/darwin-arm64)

`v0.25.8`

Compare Source

Fix another TypeScript parsing edge case (#4248)

This fixes a regression with a change in the previous release that tries to more accurately parse TypeScript arrow functions inside the ?: operator. The regression specifically involves parsing an arrow function containing a #private identifier inside the middle of a ?: ternary operator inside a class body. This was fixed by propagating private identifier state into the parser clone used to speculatively parse the arrow function body. Here is an example of some affected code:
```
class CachedDict {
  #has = (a: string) => dict.has(a);
  has = window
    ? (word: string): boolean => this.#has(word)
    : this.#has;
}
```
Fix a regression with the parsing of source phase imports

The change in the previous release to parse source phase imports failed to properly handle the following cases:
```
import source from 'bar'
import source from from 'bar'
import source type foo from 'bar'
```
Parsing for these cases should now be fixed. The first case was incorrectly treated as a syntax error because esbuild was expecting the second case. And the last case was previously allowed but is now forbidden. TypeScript hasn't added this feature yet so it remains to be seen whether the last case will be allowed, but it's safer to disallow it for now. At least Babel doesn't allow the last case when parsing TypeScript, and Babel was involved with the source phase import specification.

`v0.25.7`

Compare Source

Parse and print JavaScript imports with an explicit phase (#4238)

This release adds basic syntax support for the defer and source import phases in JavaScript:
- defer
  
  This is a stage 3 proposal for an upcoming JavaScript feature that will provide one way to eagerly load but lazily initialize imported modules. The imported module is automatically initialized on first use. Support for this syntax will also be part of the upcoming release of TypeScript 5.9. The syntax looks like this:
```
import defer * as foo from "<specifier>";
const bar = await import.defer("<specifier>");
```
  Note that this feature deliberately cannot be used with the syntax import defer foo from "<specifier>" or import defer { foo } from "<specifier>".
- source
  
  This is a stage 3 proposal for an upcoming JavaScript feature that will provide another way to eagerly load but lazily initialize imported modules. The imported module is returned in an uninitialized state. Support for this syntax may or may not be a part of TypeScript 5.9 (see this issue for details). The syntax looks like this:
```
import source foo from "<specifier>";
const bar = await import.source("<specifier>");
```
  Note that this feature deliberately cannot be used with the syntax import defer * as foo from "<specifier>" or import defer { foo } from "<specifier>".
This change only adds support for this syntax. These imports cannot currently be bundled by esbuild. To use these new features with esbuild's bundler, the imported paths must be external to the bundle and the output format must be set to esm.
Support optionally emitting absolute paths instead of relative paths (#338, #2082, #3023)

This release introduces the --abs-paths= feature which takes a comma-separated list of situations where esbuild should use absolute paths instead of relative paths. There are currently three supported situations: code (comments and string literals), log (log message text and location info), and metafile (the JSON build metadata).

Using absolute paths instead of relative paths is not the default behavior because it means that the build results are no longer machine-independent (which means builds are no longer reproducible). Absolute paths can be useful when used with certain terminal emulators that allow you to click on absolute paths in the terminal text and/or when esbuild is being automatically invoked from several different directories within the same script.
Fix a TypeScript parsing edge case (#4241)

This release fixes an edge case with parsing an arrow function in TypeScript with a return type that's in the middle of a ?: ternary operator. For example:
```
x = a ? (b) : c => d;
y = a ? (b) : c => d : e;
```
The : token in the value assigned to x pairs with the ? token, so it's not the start of a return type annotation. However, the first : token in the value assigned to y is the start of a return type annotation because after parsing the arrow function body, it turns out there's another : token that can be used to pair with the ? token. This case is notable as it's the first TypeScript edge case that esbuild has needed a backtracking parser to parse. It has been addressed by a quick hack (cloning the whole parser) as it's a rare edge case and esbuild doesn't otherwise need a backtracking parser. Hopefully this is sufficient and doesn't cause any issues.
Inline small constant strings when minifying

Previously esbuild's minifier didn't inline string constants because strings can be arbitrarily long, and this isn't necessarily a size win if the string is used more than once. Starting with this release, esbuild will now inline string constants when the length of the string is three code units or less. For example:
```
// Original code
const foo = 'foo'
console.log({ [foo]: true })

// Old output (with --minify --bundle --format=esm)
var o="foo";console.log({[o]:!0});

// New output (with --minify --bundle --format=esm)
console.log({foo:!0});
```
Note that esbuild's constant inlining only happens in very restrictive scenarios to avoid issues with TDZ handling. This change doesn't change when esbuild's constant inlining happens. It only expands the scope of it to include certain string literals in addition to numeric and boolean literals.

primer/octicons (@primer/octicons-react)

`v19.15.5`

Compare Source

Patch Changes

#1102 02cdd0c2 Thanks @CameronFoxly! - Update Loop icon for visual alignment

`v19.15.4`

Compare Source

Patch Changes

#1099 239cdee1 Thanks @CameronFoxly! - Add spaces, agents, loops, and adjust mention

`v19.15.3`

Compare Source

Patch Changes

#1097 ce04eca0 Thanks @TylerJDev! - Add outlined sparkle icon

`v19.15.2`

Compare Source

Patch Changes

#1070 795101e3 Thanks @smockle! - Add pause icon

`v19.15.1`

Compare Source

Patch Changes

#1078 8c9b6112 Thanks @francinelucca! - fix 24px id-badge asset #1048

818a40c5 Thanks @jonrohan! - Update mark-github-24 sizing #1050

`v19.15.0`

Compare Source

Minor Changes

#1063 6481783a Thanks @dylanatsmith! - Add square-circle icon

`v19.14.0`

Compare Source

Minor Changes

#1037 7402e69c Thanks @jonrohan! - Update octicons-react to use presentational attributes over inline styles for base styles

#1047 48198033 Thanks @joshblack! - Add support for SVG props to base icons

seald/nedb (@seald-io/nedb)

`v4.1.2`

Compare Source

Fixed

Add logs when errors happen in the storage backends for browser and React-Native versions.
Simplify createModifierFunction

`v4.1.1`

Compare Source

Fixed

Fix uncaught exceptions if serialization hooks throw synchronously.

`v4.1.0`

Compare Source

Feature

Remove serialization hooks tests entirely and remove the testSerializationHooks argument.
Allow the serialization hooks to be async functions.

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

`v8.38.0`

Compare Source

🩹 Fixes

disallow extra properties in rule options (#11397)
eslint-plugin: [consistent-generic-constructors] resolve conflict with isolatedDeclarations if enabled in constructor option (#11351)

❤️ Thank You

Andrew Kazakov @andreww2012
Younsang Na @nayounsang

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

`v8.37.0`

Compare Source

🩹 Fixes

eslint-plugin: [unified-signatures] fix false positives for ignoreOverloadsWithDifferentJSDoc option (#11381)

❤️ Thank You

Yukihiro Hasegawa @y-hsgw

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

`v8.36.0`

Compare Source

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

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

`v8.35.1`

Compare Source

🩹 Fixes

remove prettier from eslint-plugin (#11339)

❤️ Thank You

Abhijeet Singh @cseas

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

`v8.35.0`

Compare Source

🚀 Features

eslint-plugin: [no-base-to-string] add checkUnknown Option (#11128)

❤️ Thank You

Kim Sang Du @developer-bandi

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

`v8.34.1`

Compare Source

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

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

`v8.34.0`

Compare Source

🩹 Fixes

typescript-estree: add validation to interface extends (#11271)

❤️ Thank You

Tao

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

`v8.33.1`

Compare Source

🩹 Fixes

exclude docs/ directory from eslint-plugin package (#11251)

❤️ Thank You

roottool

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

`v8.33.0`

Compare Source

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

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

`v8.32.1`

Compare Source

🩹 Fixes

eslint-plugin: [consistent-indexed-object-style] check for indirect circular types in aliased mapped types (#11177)
eslint-plugin: [consistent-indexed-object-style] adjust auto-fixer to generate valid syntax for TSMappedType with no type annotation (#11180)
eslint-plugin: [no-deprecated] support computed member access (#10867)
eslint-plugin: [no-unnecessary-type-conversion] shouldn't have fixable property (#11194)

❤️ Thank You

Azat S. @azat-io
Dima Barabash @dbarabashh
Ronen Amiel

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

`v8.32.0`

Compare Source

🚀 Features

eslint-plugin: [only-throw-error] add option allowRethrowing (#11075)
eslint-plugin: [no-unnecessary-type-conversion] add rule (#10182)

🩹 Fixes

eslint-plugin: [prefer-nullish-coalescing] fix parenthesization bug in suggestion (#11098)
eslint-plugin: [unified-signatures] exempt this from optional parameter overload check (#11005)
eslint-plugin: [no-unnecessary-type-parameters] should parenthesize type in suggestion fixer if necessary (#10907)

❤️ Thank You

Andy Edwards
Kirk Waiblinger @kirkwaiblinger
mdm317
Sasha Kondrashov
Yukihiro Hasegawa @y-hsgw

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

`v8.31.1`

Compare Source

🩹 Fixes

eslint-plugin: [no-unnecessary-condition] downgrade fix to suggestion (#11081)

❤️ Thank You

Kirk Waiblinger @kirkwaiblinger

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

`v8.31.0`

Compare Source

🚀 Features

eslint-plugin: [no-unnecessary-type-assertion] add option to ignore string const assertions (#10979)

❤️ Thank You

Nicolas Le Cam

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

`v8.30.1`

Compare Source

🩹 Fixes

eslint-plugin: fix mistake with eslintrc config generation (#11072)

❤️ Thank You

Kirk Waiblinger @kirkwaiblinger

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

`v8.30.0`

Compare Source

🚀 Features

eslint-plugin: [no-explicit-any] suggest to replace keyof any with PropertyKey (#11032)

🩹 Fixes

eslint-plugin: [promise-function-async] use a different error message for functions with promise and non-promise types (#10950)

❤️ Thank You

Dima Barabash @dbarabashh
Ronen Amiel

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

`v8.29.1`

Compare Source

🩹 Fixes

eslint-plugin: [no-deprecated] report on deprecated imported variable used as property (#10998)

❤️ Thank You

Ronen Amiel

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

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