Skip to content

chore(deps): bump the npm-deps group across 1 directory with 9 updates#90

Open
dependabot[bot] wants to merge 1 commit into
masterfrom
dependabot/npm_and_yarn/master/npm-deps-f332fdf602
Open

chore(deps): bump the npm-deps group across 1 directory with 9 updates#90
dependabot[bot] wants to merge 1 commit into
masterfrom
dependabot/npm_and_yarn/master/npm-deps-f332fdf602

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Apr 13, 2026 •
edited
Loading

Copy link
Copy Markdown

Bumps the npm-deps group with 9 updates in the / directory:

Package From To
@fortawesome/react-fontawesome 3.2.0 3.3.0
@mui/icons-material 7.3.8 9.0.0
@mui/material 7.3.8 9.0.0
i18next 25.8.10 26.0.4
lodash 4.17.23 4.18.1
react-i18next 16.5.4 17.0.2
@vitejs/plugin-react 5.1.4 6.0.1
prettier 3.8.1 3.8.2
vite 7.3.1 8.0.8

Updates @fortawesome/react-fontawesome from 3.2.0 to 3.3.0

Release notes

Sourced from @​fortawesome/react-fontawesome's releases.

v3.3.0

3.3.0 (2026-03-20)

Highlights:

Features

Chores

CI/CD

Full Changelog: FortAwesome/react-fontawesome@v3.2.0...v3.3.0

Changelog

Sourced from @​fortawesome/react-fontawesome's changelog.

3.3.0 (2026-03-20)

Features

  • style: add support for custom gradient fills (d14cdc5)
  • style: use single prop for gradient fills, add unit tests (2282d16)

Chores

  • docs: add typedoc-generated API reference docs (5894156)
  • docs: clean up API docs output structure, rewrite html links (a7782b8)
  • docs: update README with FontAwesome documentation links (c540f90)

CI/CD

  • actions: fix publish action env setting (eb4b40a)
  • actions: only run full test matrix on PRs and main (3434d60)
  • actions: update deprecated actions (6382b20)
  • publish: enable publishing releases from CI (5d46150)
  • publish: ensure private publish uses hard main ref (f54a9c2)
Commits
  • cf9b12c chore(release): 3.3.0 [skip ci]
  • 2358c55 Merge pull request #634 from FortAwesome/chore/fix-publish-action
  • eb4b40a ci(actions): fix publish action env setting
  • e726c04 Merge pull request #633 from FortAwesome/chore/update-deprecated-actions
  • 6382b20 ci(actions): update deprecated actions
  • 2573702 Merge pull request #632 from FortAwesome/chore/docs-cleanup
  • a7782b8 chore(docs): clean up API docs output structure, rewrite html links
  • c540f90 chore(docs): update README with FontAwesome documentation links
  • 42f1d51 Merge pull request #631 from FortAwesome/feat/add-api-reference
  • 5894156 chore(docs): add typedoc-generated API reference docs
  • Additional commits viewable in compare view

Updates @mui/icons-material from 7.3.8 to 9.0.0

Release notes

Sourced from @​mui/icons-material's releases.

v9.0.0

🥳 We're excited to announce the stable release of Material UI v9.0! This major release focuses on accessibility improvements, sx prop performance, and cleanup of deprecated APIs. See the Material UI v9.0 announcement blog posts for more details. Also see the MUI v9 announcement blog posts for the broad ecosystem updates.

Check out the upgrade guide to see how you can move to this version.

@mui/material@9.0.0

Core

🙇‍♂️ We'd like to extend a big thank you to everyone involved who made this major release possible.

v9.0.0-beta.1

A big thanks to the 11 contributors who made this release possible.

@mui/material@9.0.0-beta.1

Breaking Changes

Changes

Docs

... (truncated)

Changelog

Sourced from @​mui/icons-material's changelog.

9.0.0

Apr 7, 2026

A big thanks to the 7 contributors who made this release possible.

🥳 We're excited to announce the stable release of Material UI v9! This major release focus on accessibility improvements, sx prop performance, and cleanup of deprecated APIs.

For more details, check out the upgrade guide.

@mui/material@9.0.0

Core

All contributors of this release in alphabetical order: @​brijeshb42, @​mj12albert, @​noraleonte, @​rita-codes, @​sai6855, @​silviuaavram, @​siriwatknp

9.0.0-beta.1

Apr 2, 2026

A big thanks to the 11 contributors who made this release possible.

@mui/material@9.0.0-beta.1

Breaking Changes

Changes

... (truncated)

Commits

Updates @mui/material from 7.3.8 to 9.0.0

Release notes

Sourced from @​mui/material's releases.

v9.0.0

🥳 We're excited to announce the stable release of Material UI v9.0! This major release focuses on accessibility improvements, sx prop performance, and cleanup of deprecated APIs. See the Material UI v9.0 announcement blog posts for more details. Also see the MUI v9 announcement blog posts for the broad ecosystem updates.

Check out the upgrade guide to see how you can move to this version.

@mui/material@9.0.0

Core

🙇‍♂️ We'd like to extend a big thank you to everyone involved who made this major release possible.

v9.0.0-beta.1

A big thanks to the 11 contributors who made this release possible.

@mui/material@9.0.0-beta.1

Breaking Changes

Changes

Docs

... (truncated)

Changelog

Sourced from @​mui/material's changelog.

9.0.0

Apr 7, 2026

A big thanks to the 7 contributors who made this release possible.

🥳 We're excited to announce the stable release of Material UI v9! This major release focus on accessibility improvements, sx prop performance, and cleanup of deprecated APIs.

For more details, check out the upgrade guide.

@mui/material@9.0.0

Core

All contributors of this release in alphabetical order: @​brijeshb42, @​mj12albert, @​noraleonte, @​rita-codes, @​sai6855, @​silviuaavram, @​siriwatknp

9.0.0-beta.1

Apr 2, 2026

A big thanks to the 11 contributors who made this release possible.

@mui/material@9.0.0-beta.1

Breaking Changes

Changes

... (truncated)

Commits
  • a83fd59 v9.0.0 (#48221)
  • e4de3e2 [internal] Prepare libraries for v9 stable release (#48206)
  • 2cc3f5b [transitions] Performance improvements & misc fixes (#48151)
  • af86546 [slider] Use pointer events instead of mouse events (#48164)
  • 3f1a610 [switch] Add border to make it visible in high contrast mode (#48180)
  • d7fc1c4 [internal] Sort license field to be under description
  • f1d35f6 [material-ui] Remove unnecessary overridesResolvers from styled components (#...
  • e1e43bd V9.0.0 beta.1 (#48178)
  • a2ac691 [utils] Explicitly register roving tab items with parent (#48122)
  • 56f63bf [grid] Remove 'column' and 'column-reverse' options from GridDirection type (...
  • Additional commits viewable in compare view

Updates i18next from 25.8.10 to 26.0.4

Release notes

Sourced from i18next's releases.

v26.0.4

  • fix(types): inline formatting options like {{price, currency(EUR)}} are now correctly resolved to their base format type (e.g. number for currency) instead of falling back to string 2378

v26.0.3

  • fix(types): addResourceBundle now accepts an optional 6th options parameter ({ silent?: boolean; skipCopy?: boolean }) matching the runtime API 2419

v26.0.2

  • fix(types): t("key", {} as TOptions) no longer produces a type error — the context constraint now bypasses strict checking when context is unknown (e.g. from TOptions) 2418

v26.0.1

  • fix: Formatter no longer crashes when alwaysFormat is true and no format specifier is present (format is undefined)
  • fix: Formatter now returns undefined/null values as-is instead of producing NaN when the value is missing

v26.0.0

This is a major breaking release:

Breaking Changes

  • Remove deprecated initImmediate option — the backward-compatibility mapping from initImmediate to initAsync (introduced in v24) has been removed. Use initAsync instead.
  • Remove legacy interpolation.format function — the old monolithic format function (interpolation: { format: (value, format, lng) => ... }) is no longer supported. The built-in Formatter (or a custom Formatter module via .use()) is now always used. Migrate to the new formatting approach using i18next.services.formatter.add() or .addCached() for custom formatters.
  • Remove console support notice — the console support notice introduced in v25.8.0 has been removed, along with the showSupportNotice option and all related internal suppression logic (globalThis.__i18next_supportNoticeShown, I18NEXT_NO_SUPPORT_NOTICE env var). See our blog post for the full story.
  • Remove simplifyPluralSuffix option — this option was unused by the core PluralResolver (which relies entirely on Intl.PluralRules). It only had an effect in the old v1/v2/v3 compatibility layer. The v4 test compatibility layer now defaults to true internally.
  • Remove deprecated @babel/polyfill from devDependencies.

Improvements

  • Code modernization across all source files:
    • Replace indexOf() > -1 / indexOf() < 0 with .includes() (~40+ occurrences)
    • Replace indexOf() === 0 with .startsWith() where appropriate
    • Replace var with const, '' + object with String(object), .substring() with .slice()
    • Replace .apply(observer, [event, ...args]) with direct call observer(event, ...args)
    • Remove unnecessary .call(this, ...) in BackendConnector retry logic
    • Fix array-callback-return in LanguageUtils getBestMatchFromCodes
    • Clean up all stale eslint-disable comments from source files
  • EventEmitter: add once() method for one-time event subscriptions
  • Memory leak fix: move module-level checkedLoadedFor cache to Translator instance, preventing cross-instance state leakage
  • TypeScript: fix BackendModule generic parameter naming inconsistency between CJS and ESM type definitions
  • TypeScript: add once() method to i18n and ResourceStore type interfaces
  • ESLint 9: migrate from ESLint 8 (airbnb-base) to ESLint 9 flat config with neostandard
  • Vitest 4: upgrade from vitest 3 to vitest 4, migrate workspace files to test.projects config

v25.10.10

  • feat: suppress support notice automatically in production environments (NODE_ENV=production)

v25.10.9

  • feat(types): export SelectorParam<Ns, KPrefix> helper type — a stable, readable alternative to Parameters<TFunction<Ns>>[0] for typing selector function props 2414

v25.10.8

  • fix(types): reorder TFunctionSelector overloads so Parameters<TFunction> resolves to the general selector signature instead of the branded SelectorKey type 2412

... (truncated)

Changelog

Sourced from i18next's changelog.

26.0.4

  • fix(types): inline formatting options like {{price, currency(EUR)}} are now correctly resolved to their base format type (e.g. number for currency) instead of falling back to string 2378

26.0.3

  • fix(types): addResourceBundle now accepts an optional 6th options parameter ({ silent?: boolean; skipCopy?: boolean }) matching the runtime API 2419

26.0.2

  • fix(types): t("key", {} as TOptions) no longer produces a type error — the context constraint now bypasses strict checking when context is unknown (e.g. from TOptions) 2418

26.0.1

  • fix: Formatter no longer crashes when alwaysFormat is true and no format specifier is present (format is undefined)
  • fix: Formatter now returns undefined/null values as-is instead of producing NaN when the value is missing

26.0.0

This is a major breaking release:

Breaking Changes

  • Remove deprecated initImmediate option — the backward-compatibility mapping from initImmediate to initAsync (introduced in v24) has been removed. Use initAsync instead.
  • Remove legacy interpolation.format function — the old monolithic format function (interpolation: { format: (value, format, lng) => ... }) is no longer supported. The built-in Formatter (or a custom Formatter module via .use()) is now always used. Migrate to the new formatting approach using i18next.services.formatter.add() or .addCached() for custom formatters.
  • Remove console support notice — the console support notice introduced in v25.8.0 has been removed, along with the showSupportNotice option and all related internal suppression logic (globalThis.__i18next_supportNoticeShown, I18NEXT_NO_SUPPORT_NOTICE env var). See our blog post for the full story.
  • Remove simplifyPluralSuffix option — this option was unused by the core PluralResolver (which relies entirely on Intl.PluralRules). It only had an effect in the old v1/v2/v3 compatibility layer. The v4 test compatibility layer now defaults to true internally.
  • Remove deprecated @babel/polyfill from devDependencies.

Improvements

  • Code modernization across all source files:
    • Replace indexOf() > -1 / indexOf() < 0 with .includes() (~40+ occurrences)
    • Replace indexOf() === 0 with .startsWith() where appropriate
    • Replace var with const, '' + object with String(object), .substring() with .slice()
    • Replace .apply(observer, [event, ...args]) with direct call observer(event, ...args)
    • Remove unnecessary .call(this, ...) in BackendConnector retry logic
    • Fix array-callback-return in LanguageUtils getBestMatchFromCodes
    • Clean up all stale eslint-disable comments from source files
  • EventEmitter: add once() method for one-time event subscriptions
  • Memory leak fix: move module-level checkedLoadedFor cache to Translator instance, preventing cross-instance state leakage
  • TypeScript: fix BackendModule generic parameter naming inconsistency between CJS and ESM type definitions
  • TypeScript: add once() method to i18n and ResourceStore type interfaces
  • ESLint 9: migrate from ESLint 8 (airbnb-base) to ESLint 9 flat config with neostandard
  • Vitest 4: upgrade from vitest 3 to vitest 4, migrate workspace files to test.projects config

25.10.10

  • feat: suppress support notice automatically in production environments (NODE_ENV=production)

... (truncated)

Commits

Updates lodash from 4.17.23 to 4.18.1

Release notes

Sourced from lodash's releases.

4.18.1

Bugs

Fixes a ReferenceError issue in lodash lodash-es lodash-amd and lodash.template when using the template and fromPairs functions from the modular builds. See lodash/lodash#6167

These defects were related to how lodash distributions are built from the main branch using https://github.com/lodash-archive/lodash-cli. When internal dependencies change inside lodash functions, equivalent updates need to be made to a mapping in the lodash-cli. (hey, it was ahead of its time once upon a time!). We know this, but we missed it in the last release. It's the kind of thing that passes in CI, but fails bc the build is not the same thing you tested.

There is no diff on main for this, but you can see the diffs for each of the npm packages on their respective branches:

4.18.0

v4.18.0

Full Changelog: lodash/lodash@4.17.23...4.18.0

Security

_.unset / _.omit: Fixed prototype pollution via constructor/prototype path traversal (GHSA-f23m-r3pf-42rh, fe8d32e). Previously, array-wrapped path segments and primitive roots could bypass the existing guards, allowing deletion of properties from built-in prototypes. Now constructor and prototype are blocked unconditionally as non-terminal path keys, matching baseSet. Calls that previously returned true and deleted the property now return false and leave the target untouched.

_.template: Fixed code injection via imports keys (GHSA-r5fr-rjxr-66jc, CVE-2026-4800, 879aaa9). Fixes an incomplete patch for CVE-2021-23337. The variable option was validated against reForbiddenIdentifierChars but importsKeys was left unguarded, allowing code injection via the same Function() constructor sink. imports keys containing forbidden identifier characters now throw "Invalid imports option passed into _.template".

Docs

  • Add security notice for _.template in threat model and API docs (#6099)
  • Document lower > upper behavior in _.random (#6115)
  • Fix quotes in _.compact jsdoc (#6090)

lodash.* modular packages

Diff

We have also regenerated and published a select number of the lodash.* modular packages.

These modular packages had fallen out of sync significantly from the minor/patch updates to lodash. Specifically, we have brought the following packages up to parity w/ the latest lodash release because they have had CVEs on them in the past:

Commits
  • cb0b9b9 release(patch): bump main to 4.18.1 (#6177)
  • 75535f5 chore: prune stale advisory refs (#6170)
  • 62e91bc docs: remove n_ Node.js < 6 REPL note from README (#6165)
  • 59be2de release(minor): bump to 4.18.0 (#6161)
  • af63457 fix: broken tests for _.template 879aaa9
  • 1073a76 fix: linting issues
  • 879aaa9 fix: validate imports keys in _.template
  • fe8d32e fix: block prototype pollution in baseUnset via constructor/prototype traversal
  • 18ba0a3 refactor(fromPairs): use baseAssignValue for consistent assignment (#6153)
  • b819080 ci: add dist sync validation workflow (#6137)
  • Additional commits viewable in compare view

Updates react-i18next from 16.5.4 to 17.0.2

Changelog

Sourced from react-i18next's changelog.

17.0.2

  • fix(types): values prop on <Trans /> now only requires interpolation variables for the specific i18nKey, not all variables in the namespace 1913

17.0.1

  • chore: bump minimum i18next peer dependency to >= 26.0.1 (forgot to do it in last version)
  • fix: migrate test setup from removed legacy interpolation.format to i18n.services.formatter.add() (i18next v26)

17.0.0

Potentially breaking changes

  • fix: transKeepBasicHtmlNodesFor now correctly preserves HTML tag names when children contain interpolations or mixed content 230
    • Previously, <strong>{{name}}</strong> was incorrectly serialized as <1>{{name}}</1> — the tag name was only preserved for plain string children
    • This bug existed since the feature was introduced and affects auto-generated keys (when no explicit i18nKey is provided)
    • If you rely on auto-generated Trans keys containing indexed tags for kept HTML elements with interpolation children, you will need to update your translation files

Other changes

  • updated dev dependencies (vitest, rollup plugins, happy-dom, typescript, etc.)

16.6.6

  • fix(peer-deps): bump i18next peer dependency to >= 25.10.9 to match required type exports (ConstrainTarget, ApplyTarget, GetSource) used by TransSelector 1911

16.6.5

  • fix(types): selector keyPrefix overload in useTranslation no longer matches when keyPrefix is absent, fixing defaultNS: false with explicit ns option 2412

16.6.4

  • allow TypeScript 6 as peer dependency 1910

16.6.3

  • fix(types): merge TransSelector overloads into a single signature so typeof Trans remains extendable 1909

16.6.2

  • feat(types): useTranslation now accepts selector functions as keyPrefix with full type-safe key narrowing when enableSelector is enabled 2367

16.6.1

  • feat(types): i18nKey of <Trans i18nKey={sk} /> to accept a SelectorKey 2364

16.6.0

  • warn when t is called before ready with useSuspense: false 1896
  • type-safe values prop on <Trans /> component — interpolation variables are now inferred from the translation string when custom types are configured 1772

... (truncated)

Commits
  • 4d62f86 17.0.2
  • 61fe80c fix(types): values prop on \<Trans /> now only requires interpolation vari...
  • b58d5a5 l10n: add Swedish language support to examples (#1912)
  • 2321496 17.0.1
  • 7e656b5 chore: bump minimum i18next peer dependency
  • dfc350b upate github actions
  • 7fe2620 17.0.0
  • f4ada4c fix: transKeepBasicHtmlNodesFor now correctly preserves HTML tag names when...
  • eb02c63 16.6.6
  • 76f98cd fix(peer-deps): bump i18next peer dependency to >= 25.10.9 to match require...
  • Additional commits viewable in compare viewDescription has been truncated

@dependabot
chore(deps): bump the npm-deps group across 1 directory with 9 updates
a8a557f 
Bumps the npm-deps group with 9 updates in the / directory:

| Package | From | To |
| --- | --- | --- |
| [@fortawesome/react-fontawesome](https://github.com/FortAwesome/react-fontawesome) | `3.2.0` | `3.3.0` |
| [@mui/icons-material](https://github.com/mui/material-ui/tree/HEAD/packages/mui-icons-material) | `7.3.8` | `9.0.0` |
| [@mui/material](https://github.com/mui/material-ui/tree/HEAD/packages/mui-material) | `7.3.8` | `9.0.0` |
| [i18next](https://github.com/i18next/i18next) | `25.8.10` | `26.0.4` |
| [lodash](https://github.com/lodash/lodash) | `4.17.23` | `4.18.1` |
| [react-i18next](https://github.com/i18next/react-i18next) | `16.5.4` | `17.0.2` |
| [@vitejs/plugin-react](https://github.com/vitejs/vite-plugin-react/tree/HEAD/packages/plugin-react) | `5.1.4` | `6.0.1` |
| [prettier](https://github.com/prettier/prettier) | `3.8.1` | `3.8.2` |
| [vite](https://github.com/vitejs/vite/tree/HEAD/packages/vite) | `7.3.1` | `8.0.8` |



Updates `@fortawesome/react-fontawesome` from 3.2.0 to 3.3.0
- [Release notes](https://github.com/FortAwesome/react-fontawesome/releases)
- [Changelog](https://github.com/FortAwesome/react-fontawesome/blob/main/CHANGELOG.md)
- [Commits](FortAwesome/react-fontawesome@v3.2.0...v3.3.0)

Updates `@mui/icons-material` from 7.3.8 to 9.0.0
- [Release notes](https://github.com/mui/material-ui/releases)
- [Changelog](https://github.com/mui/material-ui/blob/master/CHANGELOG.md)
- [Commits](https://github.com/mui/material-ui/commits/v9.0.0/packages/mui-icons-material)

Updates `@mui/material` from 7.3.8 to 9.0.0
- [Release notes](https://github.com/mui/material-ui/releases)
- [Changelog](https://github.com/mui/material-ui/blob/master/CHANGELOG.md)
- [Commits](https://github.com/mui/material-ui/commits/v9.0.0/packages/mui-material)

Updates `i18next` from 25.8.10 to 26.0.4
- [Release notes](https://github.com/i18next/i18next/releases)
- [Changelog](https://github.com/i18next/i18next/blob/master/CHANGELOG.md)
- [Commits](i18next/i18next@v25.8.10...v26.0.4)

Updates `lodash` from 4.17.23 to 4.18.1
- [Release notes](https://github.com/lodash/lodash/releases)
- [Commits](lodash/lodash@4.17.23...4.18.1)

Updates `react-i18next` from 16.5.4 to 17.0.2
- [Changelog](https://github.com/i18next/react-i18next/blob/master/CHANGELOG.md)
- [Commits](i18next/react-i18next@v16.5.4...v17.0.2)

Updates `@vitejs/plugin-react` from 5.1.4 to 6.0.1
- [Release notes](https://github.com/vitejs/vite-plugin-react/releases)
- [Changelog](https://github.com/vitejs/vite-plugin-react/blob/main/packages/plugin-react/CHANGELOG.md)
- [Commits](https://github.com/vitejs/vite-plugin-react/commits/plugin-react@6.0.1/packages/plugin-react)

Updates `prettier` from 3.8.1 to 3.8.2
- [Release notes](https://github.com/prettier/prettier/releases)
- [Changelog](https://github.com/prettier/prettier/blob/main/CHANGELOG.md)
- [Commits](prettier/prettier@3.8.1...3.8.2)

Updates `vite` from 7.3.1 to 8.0.8
- [Release notes](https://github.com/vitejs/vite/releases)
- [Changelog](https://github.com/vitejs/vite/blob/main/packages/vite/CHANGELOG.md)
- [Commits](https://github.com/vitejs/vite/commits/v8.0.8/packages/vite)

---
updated-dependencies:
- dependency-name: "@fortawesome/react-fontawesome"
  dependency-version: 3.3.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: npm-deps
- dependency-name: "@mui/icons-material"
  dependency-version: 9.0.0
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: npm-deps
- dependency-name: "@mui/material"
  dependency-version: 9.0.0
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: npm-deps
- dependency-name: i18next
  dependency-version: 26.0.4
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: npm-deps
- dependency-name: lodash
  dependency-version: 4.18.1
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: npm-deps
- dependency-name: react-i18next
  dependency-version: 17.0.2
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: npm-deps
- dependency-name: "@vitejs/plugin-react"
  dependency-version: 6.0.1
  dependency-type: direct:development
  update-type: version-update:semver-major
  dependency-group: npm-deps
- dependency-name: prettier
  dependency-version: 3.8.2
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: npm-deps
- dependency-name: vite
  dependency-version: 8.0.8
  dependency-type: direct:development
  update-type: version-update:semver-major
  dependency-group: npm-deps
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Apr 13, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants