Open mircealungu opened 3 months ago
How do we go about fixing this?
I think I only see material-ui in our dependencies meaning that all the others are from other packages? I think there are some breaking changes in material-ui, but I can look into updating it to v5.
It's very likely that many of these are not direct, but rather indirect dependencies. If we update all of our direct dependencies, including material indeed, we are very likely to get new versions of the indirect ones that will replace the deprecated versions. Or most of them at least... we might depend on some lazy dependencies who didn't update... but then, we should keep an eye on those!
I have tried some of them, but I still get a lot of critical issues after I do an npm audit - mainly with Babel - maybe we can look at this later.
I think this is duplicated from: https://github.com/zeeguu/web/issues/301
npm WARN deprecated babel-preset-es2015@6.24.1: π Thanks for using Babel: we recommend using babel-preset-env now: please read https://babeljs.io/env to update!
npm WARN deprecated core-js@2.6.12: core-js@<3.23.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js.
npm WARN deprecated core-js@2.6.12: core-js@<3.23.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js.
i'm getting the following errors when running
npm i
: