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

[5.6] - Switch to using a fork #24086

Merged
merged 1 commit into from
Oct 17, 2018
Merged

Conversation

legrego
Copy link
Member

@legrego legrego commented Oct 16, 2018

This backports #23422 to the 5.6 branch.

Implementation Notes

The original fix for #23422 takes advantage of yarn aliases to link to the forked version of lodash. Kibana 5.x does not use yarn, but rather npm. npm does not support aliases, so we are not able to cleanly backport this change.

We first attempted to point to the git repository directly (elastic/lodash@3.10.1-npm-kibana1), but its package.json correctly names the package @elastic/lodash. When installing this package, we end up with an @elastic/lodash directory in node_modules, rather than a lodash directory. Since we are missing the lodash directory, all import/require statements for lodash fail.

This PR solves that by publishing a nearly identical branch which is named lodash instead of @elastic/lodash: https://github.com/elastic/lodash/tree/3.10.1-npm-kibana1-5.6.

This is admittedly a hacky solution, but this is a temporary fix, and we do not anticipate making many/any changes to the 'lodash' fork for 5.6.

@elasticmachine
Copy link
Contributor

💚 Build Succeeded

@legrego legrego merged commit 8e6384f into elastic:5.6 Oct 17, 2018
@legrego legrego deleted the backport/pr23422/5.6 branch October 23, 2018 13:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants