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

Upgrade to lodash 4 #7537

Closed
xycloud opened this issue Jun 23, 2016 · 7 comments · Fixed by #69868
Closed

Upgrade to lodash 4 #7537

xycloud opened this issue Jun 23, 2016 · 7 comments · Fixed by #69868
Assignees
Labels
chore Feature:Dependencies Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc Team:Operations Team label for Operations Team

Comments

@xycloud
Copy link

xycloud commented Jun 23, 2016

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

@Bargs
Copy link
Contributor

Bargs commented Jun 23, 2016

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

@Bargs Bargs changed the title why not update lodash from 3.10.1 to 4.5.0 Upgrade to lodash 4 Jun 23, 2016
@kimjoar
Copy link
Contributor

kimjoar commented Apr 25, 2017

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.

@epixa epixa removed the P3 label Apr 25, 2017
@kobelb kobelb added the Team:Operations Team label for Operations Team label Aug 7, 2018
@jbudz jbudz added Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc and removed Team:Operations Team label for Operations Team labels Feb 7, 2019
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-platform

@lizozom
Copy link
Contributor

lizozom commented May 28, 2019

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 :)

@lizozom lizozom added the Team:Operations Team label for Operations Team label May 28, 2019
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-operations

@jbudz
Copy link
Member

jbudz commented May 29, 2019

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.

@kobelb
Copy link
Contributor

kobelb commented Oct 23, 2019

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:

I'm not really maintaining the individual method packages. We'll bump them eventually as part of one last 4.x push for security fixes but I'm in no hurry.

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
chore Feature:Dependencies Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc Team:Operations Team label for Operations Team
Projects
None yet
Development

Successfully merging a pull request may close this issue.

10 participants