Persistent baseline-browser-mapping outdated warning during next build

[yssdhiraj-4670]

Current behavior:

• During next build, I keep getting this warning multiple times:

  • [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

• This happens even after I have already installed the latest version of baseline-browser-mapping as a dev dependency.

• The build completes successfully, but the warning is repeated many times (once per worker).

VS Code Terminal logs

PS path> bun add -d baseline-browser-mapping@latest
[0.20ms] ".env.local"
bun add v1.3.2 (b131639c)

installed baseline-browser-mapping@2.9.4 with binaries:
 - baseline-browser-mapping

[2.01s] done
PS path> bun run build
$ next build
[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`
   ▲ Next.js 16.0.3 (Turbopack, Cache Components)
   - Environments: .env.local
   - Experiments (use with caution):
     · serverActions

   Creating an optimized production build ...
[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`
[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`
 ✓ Compiled successfully in 6.7s
 ✓ Finished TypeScript in 5.6s
   Collecting page data using 7 workers  ...[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`
[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`
[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`
[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`
[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`
[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`
   Collecting page data using 7 workers  .[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`
 ✓ Collecting page data using 7 workers in 1857.4ms    
[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`
home/layout.tsx
Navbar
@cart page.tsx 0
home/layout.tsx
Navbar
@cart page.tsx 0
 ✓ Generating static pages using 7 workers (6/6) in 1422.1ms
 ✓ Finalizing page optimization in 12.9ms

Route (app)
┌ ○ /
├ ○ /_not-found
├ ƒ /api/rpc/[...route]
├ ○ /error/misconfigured-auth
└ ◐ /home


ƒ Proxy (Middleware)

○  (Static)             prerendered as static content
◐  (Partial Prerender)  prerendered as static HTML with dynamic server-streamed content
ƒ  (Dynamic)            server-rendered on demand

Expected behavior:

After installing the latest version of baseline-browser-mapping, the warning should no longer appear during the build.

---

Steps to reproduce:

1. Use Next.js 16.0.3 with Turbopack.

2. Use Bun as the package manager.

3. Run:

   bun add -d baseline-browser-mapping@latest
   

4. Then run:

   bun run build
   

5. The warning about outdated baseline-browser-mapping still appears multiple times.

No custom configuration related to browser targets or baseline mapping is used.

---

Project information

• Framework: Next.js 16.0.3 (App Router, Turbopack, Cache Components)

• Package manager: Bun v1.3.2

• Node.js: Installed, but build executed via Bun

• OS: Windows 10

• Environment: .env.local

• Deployment target: Vercel (planned)

• Project type: E-commerce app using App Router + Server Actions

• Build command:

  bun run build
  

Question:
Is this warning coming from an internal copy of baseline-browser-mapping within Next.js itself? If so, is there an official way to update or suppress it safely?

[jacobparis]

This comes from BrowsersList and is harmless, but the error message has been suppressed as of Next.js 16.0.6

More discussion here

`baseline-browser-mapping` prevents reproducible builds.