Baseline Browser Mapping - module is over two months old warning?

[noaah16]

Summary

Hey!

I'm experiencing an unusual issue with the NPM plugin 'baseline-browser-mapping'. A warning is appearing that shouldn't be there.

This started happening about two days ago when I start the dev server or run a build in Next.js.

Warning:
[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

Additional information

No response

Example

No response

[icyJoseph]

Investigating this as well, I got it on my personal project. Normally you'd get a warning every now and then, that you need to update your browserslist db, every now and then, but this doesn't look like the same issue.

Adding some literature here:

• Add an environment variable to disable the "old data" warning web-platform-dx/baseline-browser-mapping#107
• baseline-browser-mapping prevents reproducible builds. web-platform-dx/baseline-browser-mapping#105

Looks like the baseline-browser-mapping package does a literal time check against its last update (?), and if its more than 2 months it starts to print this warning... Upstream issue I guess, let's track the conversation in web-platform-dx/baseline-browser-mapping#105

EDIT: Next.js already did a bump: #86625 which is included in 16.0.6

[eivindml]

How is this marked as the answer? Still happening in latest build.

[zenoshubh]

If upgrading to latest next version doesn't fix it. Try this: #86681 (comment)

[medQ-Tommy]

@zenoshubh What if we are not using pnpm and instead just npm? Is there a similar override that can be added?

[Pmacdon15]

@eivindml because there are many ways to make it go away for about 2 weeks then no matter what it's back

[zenoshubh]

@medQ-Tommy try this one: https://docs.npmjs.com/cli/v9/configuring-npm/package-json#overrides

[Pmacdon15]

I can confirm updating NextJs removes the warning.

[aliifam]

thank you

[Pmacdon15]

What good timing for bumping next lol

[hasif5]

this is really annoying, still not solved. it still keeps on, updating the package or not.

[rgbjoy]

[jakariyaa]

I can see it in 16.1.1

[phongduong-aurecon]

Same for me, currently on 16.1.4

[abue-ammar]

same here. this shit is annoying 16.1.4

[abue-ammar]

this shit appears again latest nextjs

[imrankhanpersonalai]

same error

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

[markedwards]

what is the real fix here? can this get unmarked as answered? its not resolved.

[theflucs]

I just update Next.js to 16.1.6. Before I also run yarn add -D baseline-browser-mapping@latest (just that didn't work) and the warning is not appearing anymore.

EDIT: Actually, just updating Next.js seems to be enough.

[phongduong-aurecon]

@theflucs , what we are trying to say is "it is happening even for latest version"

[theflucs]

16.1.6 is fine for me

[markedwards]

16.1.6 is not fine for me

[jonathanbc10]

16.1.6 is not fine for me either

[kpyszkowski]

Gotcha

[rin98s]

Same issue for latest version NEXTJS

[rin98s]

hmm, Issue in latest version NEXTJS

[Pmacdon15]

I'm not getting it in 16.1.6 where as I was getting it on "next": "^16.0.10"

[Pmacdon15]

I have a feeling in will be back tho lol

[rin98s]

I have update.

Update to latest version: "next": "16.1.6".

[rmartins0]

What's the status of this?

[quangdang46]

It’s still not fixed.

[trinhvanminh]

Update to "next": "16.1.6", seem solved the issue

[Pmacdon15]

I would bet you money we'll all be commenting on this in the future lol

[GemAfaWell]

Can confirm this issue still appears in 16.1.6; tried updating the package then updating everything, to no avail.

Very frustrating. I pride myself on an error-free workspace 😡

[thesunny]

If you're using PNPM, adding this to package.json fixes it for me

{
  // ...the rest of your config...
  "pnpm": {
    "overrides": {
      "baseline-browser-mapping": "latest"
    }
  }
}

I'm in a monorepo and I put it in the package.json in the root and fixes it everywhere. If you're not in a monorepo, I suspect you just put it in your lone package.json and it will fix it to.

[zenoshubh]

Ah finally! This worked for me. Thanks a lot man ;)

[Pmacdon15]

@icyJoseph is there any kind of long term fix if we are using bun ? It seems to be fixed with an update but then a few days or weeks later we have it pop up again ?

[jnroder]

Have you tried adding BASELINE_BROWSER_MAPPING_IGNORE_OLD_DATA=true to your environment variables?https://github.com/web-platform-dx/baseline-browser-mapping?tab=readme-ov-file#keeping-baseline-browser-mapping-up-to-date

Just speculating, but I think that surfacing this warning is Vercel's way of saying that:

1. Choosing what browsers your app supports is ultimately up to you, and...
2. W3C probably has a better handle on that particular problem then they do (hence their decision to use their package in the first place).

Thinking of it from the other side, what if Vercel decided to deliberately suppress warnings from a package created by the authority on browser standards whose package they use for the express purpose of deciding how to compile your code for maximally efficient support?

[Pmacdon15]

Using the env doesn't not work for me, but thank you. can you use an override with bun?

[eivindml]

Would love to see some clarity on what is best practice here. It pollutes the log.

[abue-ammar]

last time i said something they yelled at me saying it is not their fault lol

[lunarW1TCH]

Most of us literally do not care about browser mapping or can i use lite, there should be a way to disable logs or checks completely

[Pmacdon15]

OHHHHHHHH using over ride works with Bun just need to delete node mods and then Bun i

[abue-ammar]

OHHHHHHHH using over ride works with Bun just need to delete node mods and then Bun i

nope, then run bun run build and see the spam

[joziasmartini]

I used the npx @next/codemod upgrade minor and it solved the issue.

[zegenerative]

using bun, next 16.1.6, ran npx @next/codemod upgrade minor and still same issue.

[Pmacdon15]

As far as I know nothing keeps it away for long

[GemAfaWell]

Can confirm on npm specifically that finally 'npm i baseline-browser-mapping@latest -D' resolves the flag.