Planning on upgrading deprecated core-js?

[melineric]

Hi,

Current version of "core-js": "^3.6.5", is deprecated. https://www.npmjs.com/package/core-js/v/3.6.5?activeTab=versions

Are you planning in upgrading to a supported version in the near future?

Author message:
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.

Best regards,
Eric

[gzuidhof]

I'm not sure if we are even including anything from core-js (maybe Babel depends on it?) - so I think we can definitely remove or upgrade it. For this reason I don't think this library is affected by any slowdowns, making it low priority for now - but it's definitely to do.

[JTBrinkmann]

Even though core-js already declares a newer core-js as direct dependency, the babel version it still uses transitively pulls in the deprecated core-js.

[JTBrinkmann]

on that note, friendly-challenge does indeed declare dependencies that are completely unused. promis, whatwg-fetch, url-polyfill, and object-assign-polyfill are embedded inside polyfills.min.js, additionally pulling them in as a dependency services no purpose. Maybe at least moving them to dev dependencies would help, so they aren't pulled in by everyone using friendly-challange. I don't think it's a big issue either way.