When will the code be updated to fix and remove these deprecated objects/assets?
This is the yarn out put of a fresh install after being updated to the latest

"yarn upgrade --latest"

Am I supposed to work out which pieces of code were custom to support this theme and re-write those components with updated packages?

Any thougths?


warning package-lock.json found. Your project contains lock files generated by tools other than Yarn. It is advised not to mix package managers in order to avoid resolution inconsistencies caused by unsynchronized lock files. To clear this warning, remove package-lock.json.
warning keenthemes@3.0.8: No license field
[1/4] 🔍 Resolving packages...
warning extract-loader > babel-runtime > 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.
warning extract-loader > babel-core > babel-register > 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.
warning gulp-sourcemaps > css > source-map-resolve@0.6.0: See https://github.com/lydell/source-map-resolve#deprecated
warning rtlcss-webpack-plugin > babel-runtime > 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.
warning webpack-merge-and-include-globally > glob@7.2.3: Glob versions prior to v9 are no longer supported
warning webpack-merge-and-include-globally > glob > inflight@1.0.6: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
[2/4] 🚚 Fetching packages...
warning chart.js@4.4.7: The engine "pnpm" appears to be invalid.
[3/4] 🔗 Linking dependencies...
warning " > @yaireo/tagify@4.33.0" has unmet peer dependency "prop-types@>15.5.7".
warning " > @yaireo/tagify@4.33.0" has unmet peer dependency "react@*".
warning " > @yaireo/tagify@4.33.0" has unmet peer dependency "react-dom@*".
warning " > vis-timeline@7.7.3" has unmet peer dependency "@egjs/hammerjs@^2.0.0".
warning " > vis-timeline@7.7.3" has unmet peer dependency "component-emitter@^1.3.0".
warning " > vis-timeline@7.7.3" has unmet peer dependency "keycharm@^0.2.0 || ^0.3.0 || ^0.4.0".
warning " > vis-timeline@7.7.3" has unmet peer dependency "propagating-hammerjs@^1.4.0 || ^2.0.0".
warning " > vis-timeline@7.7.3" has unmet peer dependency "uuid@^3.4.0 || ^7.0.0 || ^8.0.0 || ^9.0.0".
warning " > vis-timeline@7.7.3" has unmet peer dependency "vis-data@^6.3.0 || ^7.0.0".
warning " > vis-timeline@7.7.3" has unmet peer dependency "vis-util@^5.0.1".
warning " > vis-timeline@7.7.3" has unmet peer dependency "xss@^1.0.0".
warning " > postcss-loader@8.1.1" has unmet peer dependency "postcss@^7.0.0 || ^8.0.1".