Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix outdated warning "Browserslist: caniuse-lite is outdated ..." during "npm build"! #55

Closed
vamcart opened this issue Feb 14, 2019 · 10 comments
Projects

Comments

@vamcart
Copy link
Member

vamcart commented Feb 14, 2019

Browserslist: caniuse-lite is outdated. Please run next command npm update caniuse-lite browserslist

Looks like this dependency from "babel-preset-env" package from package.json

Maybe to update babel packages in package.json

@Pfurr
Copy link

Pfurr commented Feb 14, 2019

yeah, i add it manually (it need to update all json package)

@vamcart
Copy link
Member Author

vamcart commented Feb 15, 2019

@ngoyal16 ngoyal16 added this to To do in v1.0 Feb 18, 2019
@vamcart
Copy link
Member Author

vamcart commented Feb 18, 2019

Why package-lock.json file located in repository?!
As i know, it's a automatic generated file after "npm install" command.
Auto-generated files and dependency packages should not be in repository as i know!

@vamcart
Copy link
Member Author

vamcart commented Feb 18, 2019

and here is the answer - https://stackoverflow.com/questions/48524417/should-the-package-lock-json-file-be-added-to-gitignore

and another opinion for not include auto generated lock file at repository - https://stackoverflow.com/questions/44206782/do-i-commit-the-package-lock-json-file-created-by-npm-5

@vamcart
Copy link
Member Author

vamcart commented Feb 18, 2019

cezerin store (catalog) side don't work without package-lock.json file.
I try to delete lock file and run: "npm install; npm run build; npm start"
API and Dashboard works fine, but store (catalog side) has error:

Cannot read property 'replace' of null

@vamcart
Copy link
Member Author

vamcart commented Mar 25, 2019

Here is updated package-json.lock files in archive.

With that updated files all warnings was fixed.

cezerin2-package-json-lock.zip

@vamcart vamcart closed this as completed Mar 25, 2019
@biruelrick
Copy link

In my case this works fine...

sudo npm i -g browserslist caniuse-lite

@shaikfareed64
Copy link

Surprisingly just yarn install worked for me. Wonder why

@flavianh
Copy link

flavianh commented Jan 8, 2020

@vamcart You know that both links you posted have the top answer saying "Add the package-lock.json you to your version control repository" in https://stackoverflow.com/questions/48524417/should-the-package-lock-json-file-be-added-to-gitignore and "Yes, package-lock.json is intended to be checked into source control." in https://stackoverflow.com/questions/44206782/do-i-commit-the-package-lock-json-file-created-by-npm-5

@progrookie
Copy link

yarn upgrade solved my problem...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
No open projects
v1.0
  
To do
Development

No branches or pull requests

6 participants