Skip to content

Next 16.0.11 emits a [baseline-browser-mapping] The data in this module is over two months old. warning #89190

@eliw00d

Description

@eliw00d

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    create-next-appRelated to our CLI tool for quickly starting a new Next.js application.

    Type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions