Skip to content

Bump js-yaml, @nuxtjs/i18n and husky - #223

Open
dependabot[bot] wants to merge 1 commit into
masterfrom
dependabot/npm_and_yarn/multi-e1b3f5e382
Open

dependabot[bot] wants to merge 1 commit into
masterfrom
dependabot/npm_and_yarn/multi-e1b3f5e382

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Aug 10, 2026

Copy link
Copy Markdown
Contributor

Bumps js-yaml to 4.3.1 and updates ancestor dependencies js-yaml, @nuxtjs/i18n and husky. These dependencies need to be updated together.

Updates js-yaml from 4.1.1 to 4.3.1

Changelog

Sourced from js-yaml's changelog.

4.3.1 - 2026-07-31

Security

  • [backport] Remove quadratic complexity from !!omap duplicate key detection.

4.3.0 - 2026-06-27

Added

  • [backport] Added maxTotalMergeKeys (10000) loader option to limit the total number of keys processed by YAML merge (<<) across one load() / loadAll() call.

Fixed

  • Restore umd builds back to es5.

Removed

  • [backport] maxMergeSeqLength replaced with maxTotalMergeKeys for limiting YAML merge processing.

[4.2.0] - 2026-06-01

Added

  • Added docs/safety.md with notes about processing untrusted YAML.
  • Added maxDepth (100) loader option. Not a problem, but gives a better exception instead of RangeError on stack overflow.
  • Added maxMergeSeqLength (20) loader option. Not a problem after merge fix, but an additional restriction for safety.
  • Added sourcemaps to dist/ builds.

Changed

  • Stop resolving numbers with underscores as numeric scalars, #627.
  • Switched dev toolchains to Vite / neostandard.
  • Updated demo.
  • Reorganized tests.
  • dist/ files are no longer kept in the repository.

Fixed

  • Fix parsing of properties on the first implicit block mapping key, #62.
  • Fix trailing whitespace handling when folding flow scalar lines, #307.
  • Reject top-level block scalars without content indentation, #280.
  • Ensure numbers survive round-trip, #737.
  • Fix test coverage for issue #221.
  • Fix flow scalar trailing whitespace folding, #307.
  • Fix digits in YAML named tag handles.

Security

  • Fix potential DoS via quadratic complexity in merge - deduplicate repeated elements (makes sense for malformed files > 10K).

[3.14.2] - 2025-11-15

Security

... (truncated)

Commits
  • 86e91b8 4.3.1 released
  • c3cc4b0 Backport quadratic complexity fix for !!omap
  • 33d05b5 4.3.0 released
  • 663bfab Drop demo publish, to not override new v5 one.
  • 1cb8c7b Add v4-legacy tag for publish
  • 02f27af Restore umd builds back to es5
  • 8be84ed Fix es5 compatibility
  • 59423c6 Replace maxMergeSeqLength option with maxTotalMergeKeys (more robust). Ba...
  • 6842ef6 doc polish
  • 590dbab 4.2.0 released
  • Additional commits viewable in compare view

Updates @nuxtjs/i18n from 7.3.1 to 10.6.0

Release notes

Sourced from @​nuxtjs/i18n's releases.

v10.6.0

This release is mostly about performance, and about making the domain features behave consistently.

Faster builds and faster SSR

Locale messages are no longer bundled into your server build as JavaScript, no longer shipped as client chunks when they are served from the messages endpoint, and no longer copied on every server-rendered request.

Building a Nuxt app with 10 locales of around 2,000 messages each and 10 pages:

10.5.0 10.6.0
build time 9.2s 5.7s 38% faster
peak build memory 3.6 GB 2.5 GB 30% less
build output added by the module 12.9 MB 3.2 MB 75% smaller
SSR throughput 785 req/s 1722 req/s 2.2× higher

Median of three runs on an M4 Pro with Nuxt 4.5; throughput over 10 concurrent connections. The same app without the module builds in 3.4s and outputs 3.2 MB.

How much of this you notice depends on how many messages your app loads: a few locales with a few hundred messages each will barely differ, larger message sets gain the most. It covers messages the module can read while building — .json, .yaml and .json5 files. Locale files written as .ts or .js produce their messages at runtime, so both their build and their SSR cost stay as they were. Apps that previously ran out of memory building large message sets should now complete.

This should work without any changes on your side. The new message handling can be turned off with experimental.optimizeMessageBundling: false if you run into trouble — and if you do, please let us know so we can sort it out.

Domains

differentDomains and multiDomainLocales now agree on which locale each domain serves, which URL a locale is advertised on, and where a visitor goes when the locale they asked for lives on another domain. hreflang and canonical links name one domain per locale, so every domain in your setup describes the same set of pages instead of each claiming the languages for itself.

10.5.0 could also stop serving a locale at its own domain root, redirecting / to the prefixed path and returning 404 for unprefixed paths. A domain that serves exactly one locale is treated as that locale's default again, so domainDefault is not needed for it.

Changelog

   🚀 Features

   🐞 Bug Fixes

... (truncated)

Changelog

Sourced from @​nuxtjs/i18n's changelog.

v10.6.0 (2026-07-30T10:49:10Z)

This changelog is generated by GitHub Releases

   🚀 Features

   🐞 Bug Fixes

   🏎 Performance

    View changes on GitHub

v10.5.0 (2026-07-21T14:05:18Z)

... (truncated)

Commits
  • 4c36bc9 release: v10.6.0
  • d17b9be refactor(routing): drop the unreachable on-host prefix strip (#4111)
  • ca32d4d docs: describe what the domain override cannot change and which links cross o...
  • 285f2d6 test: poll message counts instead of reading them once after a locale fetch (...
  • 187b364 fix(domain): serve every locale on a host matching no configured domain (#4108)
  • efb9d50 fix(domain): resolve a domain serving a single locale as its default (#4107)
  • 21e1ccd fix(seo): resolve alternate and canonical links from one domain per locale (#...
  • d6930a6 fix(types): prevent duplicate tsconfig paths for aliased deps (#4031)
  • 03eba9f fix(domain): redirect detection to the domain serving the detected locale (#4...
  • a4eee0f fix: keep params encoded when resolving a localized route by path (#4104)
  • Additional commits viewable in compare view
Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for @​nuxtjs/i18n since your current version.


Updates husky from 2.7.0 to 9.1.7

Release notes

Sourced from husky's releases.

v9.1.7

What's Changed

New Contributors

Full Changelog: typicode/husky@v9.1.6...v9.1.7

v9.1.6

What's Changed

New Contributors

Full Changelog: typicode/husky@v9.1.5...v9.1.6

v9.1.5

What's Changed

New Contributors

Full Changelog: typicode/husky@v9.1.4...v9.1.5

v9.1.4

  • Improve deprecation notice

v9.1.3

  • fix: better handle space in PATH

v9.1.2

Show a message instead of automatically removing deprecated code.

This only concerns projects that still have the following code in their hooks:

- #!/usr/bin/env sh # <- This is deprecated, remove it
- . "$(dirname -- "$0")/_/husky.sh"  # <- This is deprecated, remove it
Rest of your hook code

Hooks with these lines will fail in v10.0.0

v9.1.1

... (truncated)

Commits

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    You can disable automated security fix PRs for this repo from the Security Alerts page.

Bumps [js-yaml](https://github.com/nodeca/js-yaml) to 4.3.1 and updates ancestor dependencies [js-yaml](https://github.com/nodeca/js-yaml), [@nuxtjs/i18n](https://github.com/nuxt-modules/i18n) and [husky](https://github.com/typicode/husky). These dependencies need to be updated together.


Updates `js-yaml` from 4.1.1 to 4.3.1
- [Changelog](https://github.com/nodeca/js-yaml/blob/4.3.1/CHANGELOG.md)
- [Commits](nodeca/js-yaml@4.1.1...4.3.1)

Updates `@nuxtjs/i18n` from 7.3.1 to 10.6.0
- [Release notes](https://github.com/nuxt-modules/i18n/releases)
- [Changelog](https://github.com/nuxt-modules/i18n/blob/main/CHANGELOG.md)
- [Commits](nuxt-modules/i18n@v7.3.1...v10.6.0)

Updates `husky` from 2.7.0 to 9.1.7
- [Release notes](https://github.com/typicode/husky/releases)
- [Commits](https://github.com/typicode/husky/commits/v9.1.7)

---
updated-dependencies:
- dependency-name: js-yaml
  dependency-version: 4.3.1
  dependency-type: indirect
- dependency-name: "@nuxtjs/i18n"
  dependency-version: 10.6.0
  dependency-type: direct:production
- dependency-name: husky
  dependency-version: 9.1.7
  dependency-type: direct:development
...

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 Aug 10, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants