Update browserlist DB for caniuse-lite

[peterwilsoncc]

Describe the bug

During an npm install an alert is shown that the caniuse browserlist database is out of date. It can be updated by running npx browserslist@latest --update-db.

This will help reduce redundant JS and CSS required to support unsupported browsers.

Steps to Reproduce

1. Clone the repository
2. Run npm i; npm run build
3. During this process a warning will be shown:

   Browserslist: caniuse-lite is outdated. Please run:
   npx browserslist@latest --update-db
   Why you should do it regularly: https://github.com/browserslist/browserslist#browsers-data-updating
   

Screenshots, screen recording, code snippet

No response

Environment information

No response

WordPress information

No response

Code of Conduct

• I agree to follow this project's Code of Conduct

[punndcoder28]

Hi @peterwilsoncc from my cursory understanding of the library and it's workings, shouldn't this be done locally? Or does it need to be updated in the project?

[peterwilsoncc]

@punndcoder28 You run the command above locally to update the package-lock.json file to refer the latest database. You can see an equivalent PR on Distributor 10up/distributor#1059

[punndcoder28]

Thanks for pointing out how it should be done. I ran the following commands as suggested in the issue description which results in the error mentioned here. I also do not want to run the install command with --legacy-peer-deps as it might lead to other dependency related issues with the project. Here are my npm and node versions

npm: 8.19.3
node: 19.2.0

Should I use any other version than the ones mentioned above?

[peterwilsoncc]

It looks like the GitHub actions run using node 12 so maybe give that a try. The linked npm version appears to be around 6.14.16. If you haven't got a node version manager installed already then https://github.com/Schniz/fnm/ is great.

publisher-media-kit/.github/workflows/lint.yml

Lines 22 to 25 in 7c3c640

	- name: install node v12
	uses: actions/setup-node@v1
	with:
	node-version: 12

[punndcoder28]

Ended up using nvm since it was already on my machine. Will be sending out a PR from my forked repo.

[punndcoder28]

I have opened up PR #150 which should fix this issue.