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

deduplicate yarn.lock #32760

Closed
wants to merge 18 commits into from
Closed

deduplicate yarn.lock #32760

wants to merge 18 commits into from

Conversation

jbudz
Copy link
Member

@jbudz jbudz commented Mar 8, 2019

This removes duplicate entries in our lock file using https://github.com/atlassian/yarn-deduplicate. Over time new packages aren't squashed as much as they could by yarn add. Regenerating yarn.lock does fix this, but it's a significantly larger change as all dependencies are updated according to their semver rules with what's released. It leaves a lot to sort comparative to squashing statically with this approach, based on what's in the file.

We ran into one issue with canvas based on an upgraded react types packages and a still open issue. I'll leave it up to the canvas team what we do here, I can rollback that one package or remove the type check, or some alternative.

@jbudz jbudz added review Team:Operations Team label for Operations Team labels Mar 8, 2019
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-operations

@elasticmachine
Copy link
Contributor

💔 Build Failed

@tylersmalley
Copy link
Contributor

@jbudz can you add a description and the versions targeting? Did you use a script to de-dupe?

@jbudz jbudz requested a review from a team as a code owner March 13, 2019 22:23
@elasticmachine
Copy link
Contributor

💔 Build Failed

@elasticmachine
Copy link
Contributor

💔 Build Failed

Copy link
Member

@mistic mistic left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Copy link
Contributor

@w33ble w33ble left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That DefinitelyTyped bug is annoying, but it is what it is I guess. We're planning to rip out all the propType stuff once we're using TS anyway. Hopefully this makes bootstrapping a little faster and the bundle a little smaller too.

@elasticmachine
Copy link
Contributor

💔 Build Failed

@elasticmachine
Copy link
Contributor

💔 Build Failed

@jbudz
Copy link
Member Author

jbudz commented Mar 21, 2019

retest

@jbudz jbudz closed this Mar 21, 2019
@jbudz jbudz reopened this Mar 21, 2019
@elasticmachine
Copy link
Contributor

💔 Build Failed

@elasticmachine
Copy link
Contributor

💔 Build Failed

@elasticmachine
Copy link
Contributor

💔 Build Failed

@jbudz jbudz added the non-issue Indicates to automation that a pull request should not appear in the release notes label Mar 27, 2019
@tylersmalley
Copy link
Contributor

Want to try to go at this again?

@elasticmachine
Copy link
Contributor

💔 Build Failed

@elasticmachine
Copy link
Contributor

💔 Build Failed

@elasticmachine
Copy link
Contributor

💔 Build Failed

@elasticmachine
Copy link
Contributor

💔 Build Failed

@elasticmachine
Copy link
Contributor

💔 Build Failed

@elasticmachine
Copy link
Contributor

💔 Build Failed

@jbudz
Copy link
Member Author

jbudz commented May 22, 2019

Closing this out for now, there's some parallel efforts that spalger is undertaking.

@jbudz jbudz closed this May 22, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
non-issue Indicates to automation that a pull request should not appear in the release notes review Team:Operations Team label for Operations Team v7.2.0 v8.0.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants