-
SummaryHey! 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: Additional informationNo response ExampleNo response |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 3 replies
-
|
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:
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... EDIT: Next.js already did a bump: #86625 which is included in 16.0.6 |
Beta Was this translation helpful? Give feedback.
-
|
I can confirm updating NextJs removes the warning. |
Beta Was this translation helpful? Give feedback.
-
|
What good timing for bumping next lol |
Beta Was this translation helpful? Give feedback.
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:
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...
Upstreamissue I guess, let's track the conversation in web-platform-dx/baseline-browser-mapping#105EDIT: Next.js already did a bump: #86625 which is included in 16.0.6