Issue Station
Sign In
Tools hereToolbox

nextjs - ✅(Solved) Fix Next 16.0.11 emits a `[baseline-browser-mapping] The data in this module is over two months old.` warning [2 pull requests, 6 comments, 6 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
vercel/next.js#89190•Fetched 2026-04-08 02:03:11
View on GitHub
Comments
6
Participants
6
Timeline
17
Reactions
3
Author
eliw00deliw00d
Participants
eliw00deliw00dgithub-actions[bot]github-actions[bot]HiRahmatDevHiRahmatDevjimrandomhjimrandomhlukesandberglukesandbergnehaaprasadnehaaprasad
Timeline (top)
commented ×6cross-referenced ×2labeled ×2subscribed ×2

Fix Action

Fixed

PR fix notes

PR #89224: fix: suppress baseline-browser-mapping stale-data warning

Description (problem / solution / changelog)

  • What?

Stops the [baseline-browser-mapping] The data in this module is over two months old warning from showing for next dev, next build, and next info.

  • Why? browserslist (used by Next) can load baseline-browser-mapping, which prints that warning when its data is old. It’s noisy and not useful for most users.

  • How? Set BASELINE_BROWSER_MAPPING_IGNORE_OLD_DATA=1 in require-hook.ts at startup when the env var isn’t already set.

Fixes #89190

Changed files

  • packages/next/src/server/require-hook.ts (modified, +4/-0)

PR #89259: fix: backport baseline-browser-mapping changes to 16.0

Description (problem / solution / changelog)

closes #89190

Changed files

  • .github/workflows/build_reusable.yml (modified, +4/-0)
  • packages/next/package.json (modified, +1/-0)
  • packages/next/taskfile.js (modified, +3/-1)
  • pnpm-lock.yaml (modified, +26/-23)

Code Example

[baseline-browser-mapping] The data in this module is over two months old.  To ensure accurate Baseline data, please update: `npm i baseline-browser-mapping@latest -D`

---

❯ npx next info
[baseline-browser-mapping] The data in this module is over two months old.  To ensure accurate Baseline data, please update: `npm i baseline-browser-mapping@latest -D`

Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 25.2.0: Tue Nov 18 21:09:41 PST 2025; root:xnu-12377.61.12~1/RELEASE_ARM64_T6031
  Available memory (MB): 65536
  Available CPU cores: 16
Binaries:
  Node: 24.11.1
  npm: 11.6.2
  Yarn: 1.22.22
  pnpm: 10.25.0
Relevant Packages:
  next: 16.0.11 // There is a newer version (16.1.6) available, upgrade recommended! 
  eslint-config-next: N/A
  react: 19.2.3
  react-dom: 19.2.3
  typescript: 5.9.3
Next.js Config:
  output: N/A
 ⚠ There is a newer version (16.1.6) available, upgrade recommended! 
   Please try the latest canary version (`npm install next@canary`) to confirm the issue still exists before creating a new issue.
   Read more - https://nextjs.org/docs/messages/opening-an-issue
RAW_BUFFERClick to expand / collapse

Link to the code that reproduces this issue

https://github.com/eliw00d/next-baseline-browser-mapping-repro

To Reproduce

  1. npm i
  2. npm run build or npm run dev
  3. See:
[baseline-browser-mapping] The data in this module is over two months old.  To ensure accurate Baseline data, please update: `npm i baseline-browser-mapping@latest -D`

Current vs. Expected behavior

Current behavior

16.0.11 emits a [baseline-browser-mapping] The data in this module is over two months old. warning. 16.1.6 does not emit this warning.

Expected behavior

A new release of 16.0 that does not emit a [baseline-browser-mapping] The data in this module is over two months old. warning.

Provide environment information

❯ npx next info
[baseline-browser-mapping] The data in this module is over two months old.  To ensure accurate Baseline data, please update: `npm i baseline-browser-mapping@latest -D`

Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 25.2.0: Tue Nov 18 21:09:41 PST 2025; root:xnu-12377.61.12~1/RELEASE_ARM64_T6031
  Available memory (MB): 65536
  Available CPU cores: 16
Binaries:
  Node: 24.11.1
  npm: 11.6.2
  Yarn: 1.22.22
  pnpm: 10.25.0
Relevant Packages:
  next: 16.0.11 // There is a newer version (16.1.6) available, upgrade recommended! 
  eslint-config-next: N/A
  react: 19.2.3
  react-dom: 19.2.3
  typescript: 5.9.3
Next.js Config:
  output: N/A
 ⚠ There is a newer version (16.1.6) available, upgrade recommended! 
   Please try the latest canary version (`npm install next@canary`) to confirm the issue still exists before creating a new issue.
   Read more - https://nextjs.org/docs/messages/opening-an-issue

Which area(s) are affected? (Select all that apply)

create-next-app

Which stage(s) are affected? (Select all that apply)

next dev (local), next build (local)

Additional context

We are currently blocked on upgrading to Next 16.1 due to our use of Rush.js so we have to stay on 16.0 for now. A new release of 16.0 with this fixed would be great.

extent analysis

TL;DR

Update baseline-browser-mapping to the latest version using npm i baseline-browser-mapping@latest -D to potentially resolve the warning issue.

Guidance

  • The warning message suggests that the data in the baseline-browser-mapping module is over two months old, which may cause inaccurate Baseline data.
  • To mitigate this issue, try updating baseline-browser-mapping to the latest version as suggested in the warning message.
  • Since upgrading to Next 16.1 is not currently possible due to Rush.js constraints, focusing on updating baseline-browser-mapping might provide a workaround for the warning on Next 16.0.
  • Verify if the update resolves the warning by running npm run build or npm run dev after updating baseline-browser-mapping.

Notes

The issue seems to be related to the version of baseline-browser-mapping rather than Next.js itself, given that the warning disappears in Next 16.1.6 but the question asks for a solution on Next 16.0.

Recommendation

Apply workaround: Update baseline-browser-mapping to the latest version, as this directly addresses the cause of the warning and might resolve the issue without requiring an upgrade to Next 16.1.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#dependency conflict#environment setup#docker error#permission error#memory optimization

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING