Update dependency @nuxt/fonts to ^0.14.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@nuxt/fonts	^0.11.4 → ^0.14.0

---

Release Notes

nuxt/fonts (@​nuxt/fonts)

v0.14.0

Compare Source

0.14.0 is the next minor release.

🚨 Breaking changes

Default font format is now woff2 only

Font providers previously returned multiple formats (woff2, woff, truetype, etc.). The default behavior now only resolves woff2 fonts, which is supported by all modern browsers.

Your @font-face declarations will typically have fewer src entries, reducing CSS size. In most cases this is a transparent improvement.

To restore the previous behavior or add additional formats:

export default defineNuxtConfig({
  fonts: {
    defaults: {
      formats: ['woff2', 'woff', 'ttf'],
    },
  },
})

Available values: 'woff2', 'woff', 'ttf', 'otf', 'eot'.

Cache invalidation

Font metadata caches are now isolated per provider and per provider options. After upgrading, your font metadata cache (node_modules/.cache/nuxt/fonts/) will be invalidated and fonts will be re-fetched on the next build. This is a one-time occurrence.

✨ Features

Resolve fonts from node_modules

A new built-in npm provider can resolve fonts installed as npm packages. If no other provider matches a font family, @nuxt/fonts will now attempt to find it in your node_modules via CDN metadata.

export default defineNuxtConfig({
  fonts: {
    npm: {
      // options for the npm provider (optional)
    },
  },
})

Font format resolution

You can control which font formats are resolved via the new defaults.formats option:

export default defineNuxtConfig({
  fonts: {
    defaults: {
      formats: ['woff2'], // default
    },
  },
})

Provider-specific font family options

You can now pass provider-specific options when configuring individual font families:

export default defineNuxtConfig({
  fonts: {
    families: [
      {
        name: 'My Font',
        provider: 'google',
        providerOptions: {
          google: {
            // provider-specific options for this family
          },
        },
      },
    ],
  },
})

throwOnError option

Configure whether font resolution errors should throw or warn:

export default defineNuxtConfig({
  fonts: {
    throwOnError: true, // default: false
  },
})

lightningcss support

If your Nuxt project uses Vite's lightningcss mode for CSS processing (for example, if you're using rolldown-vite!), injected @font-face declarations are now minified with lightningcss instead of esbuild.

🩹 Fixes

• Prevent font flashes in development — The dev font proxy now returns Cache-Control: public, max-age=31536000, immutable headers, preventing font flashes during HMR on SSR frameworks.
• Broader CSS file matching — Font family injection now matches additional CSS-like file patterns (Vue SFC &lang.css query strings and inline style IDs), aligning with fontless behavior.
• Adobe provider race condition — Fixed a race condition in the Adobe (Typekit) provider where concurrent font resolution could clear the font family map mid-flight, causing Adobe fonts to silently fail. (fix in unifont 0.7.4)
• Prioritize sliced woff2 over full ttf — When both formats are available, woff2 subsets are now correctly prioritized over full ttf files. (fix in unifont 0.7.2)
• Bunny provider subset filtering — The Bunny font provider now correctly filters by subsets. (fix in unifont 0.7.0)

👉 Changelog

compare changes

🚀 Enhancements

• Upgrade to the latest versions fontless + unifont (3d634b0)
• Support lightningcss transforms (171c9a4)
• Add support for resolving fonts from local node_modules (#​781)

🩹 Fixes

• Prevent font flashes in development (0ec437e)
• Include more css-ish files when injecting font-families (6e8e343)
• deps: Bump unifont + reenable adobe tests (9d7715d)

📖 Documentation

• Add nuxt.care health badge (8f0a978)

🏡 Chore

• Fix changelog workflow (#​776)
• Remove changelog (in favour of github releases) (25c87c4)

✅ Tests

• Update snapshots for adobe preloads (035091a)

🤖 CI

• Pin github actions to full-length commit shas (18e3ff7)

❤️ Contributors

• Daniel Roe (@​danielroe)
• Bjorn Lu (@​bluwy)

v0.13.0

Compare Source

v0.12.1

Compare Source

0.12.1 is the next patch release.

This is a rerelease of 0.12.0, which encountered an issue in the publishing process. See release notes for v0.12.0.

👉 Changelog

compare changes

🏡 Chore

• Update workspace version for devtools (#​724)

❤️ Contributors

• Alexandru Teodor (@​alexieremia)

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• 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.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

npm warn Unknown env config "store". This will stop working in the next major version of npm. See `npm help npmrc` for supported config options.
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: next-auth@4.21.1
npm error Found: nodemailer@7.0.6
npm error node_modules/nodemailer
npm error   nodemailer@"^7.0.6" from the root project
npm error
npm error Could not resolve dependency:
npm error peerOptional nodemailer@"^6.6.5" from next-auth@4.21.1
npm error node_modules/next-auth
npm error   next-auth@"~4.21.1" from the root project
npm error   peer next-auth@"~4.21.1" from @sidebase/nuxt-auth@1.1.0
npm error   node_modules/@sidebase/nuxt-auth
npm error     @sidebase/nuxt-auth@"1.1.0" from the root project
npm error     1 more (@dcc-bs/authentication.bs.js)
npm error
npm error Conflicting peer dependency: nodemailer@6.10.1
npm error node_modules/nodemailer
npm error   peerOptional nodemailer@"^6.6.5" from next-auth@4.21.1
npm error   node_modules/next-auth
npm error     next-auth@"~4.21.1" from the root project
npm error     peer next-auth@"~4.21.1" from @sidebase/nuxt-auth@1.1.0
npm error     node_modules/@sidebase/nuxt-auth
npm error       @sidebase/nuxt-auth@"1.1.0" from the root project
npm error       1 more (@dcc-bs/authentication.bs.js)
npm error
npm error Fix the upstream dependency conflict, or retry this command with --force or --legacy-peer-deps to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2026-05-13T03_13_18_896Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-05-13T03_13_18_896Z-debug-0.log