-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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
Upgrade to lodash 4 #7537
Comments
I don't know if anyone has taken a swing at it and encountered specific issues, but my guess is that it just hasn't been worth it to deal with all the breaking changes yet. It's true that there are a lot of new methods in 4.x, but _.isEmpty is actually available in 3.x btw: https://github.com/lodash/lodash/blob/3.10.1/doc/README.md#_isemptyvalue |
Btw, https://github.com/jfmengels/lodash-codemods is possibly a good starting point for this. /cc @archanid as I think I remember you've mentioned interest in codemods earlier. This could be an interesting fix to play around with them. |
Pinging @elastic/kibana-platform |
After speaking to @kobelb, I understand we are using a forked 3.x because of https://hackerone.com/reports/310443 However, 4.x is now patched as well, and it should be possible to upgrade to 4.x :) |
Pinging @elastic/kibana-operations |
Yup, the fork for the security fix and the pending upgrade to v4 is mostly due to how many uses we have. It's a lot of breaking changes IIRC. |
To work-around the out of date version of lodash, there has been the occasional usage of the "per-method packages", for example lodash.clonedeep. These will be going away in lodash version 5. Additionally, they generally lag behind when there is a security vulnerability and per the main author of lodash:
We really need to figure out a plan here. We're already maintaining a fork of lodash@3 and version 5 is now in the works. |
VERSION: kibana 5.0
why not update lodash from 3.10.1 to 4.5.0? some function only existed in 4.5.0 like _.isEmpty
The text was updated successfully, but these errors were encountered: