-
Notifications
You must be signed in to change notification settings - Fork 14k
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
Add yarn.lock #4674
Add yarn.lock #4674
Conversation
Codecov Report
@@ Coverage Diff @@
## master #4674 +/- ##
=======================================
Coverage 71.37% 71.37%
=======================================
Files 190 190
Lines 14918 14918
Branches 1102 1102
=======================================
Hits 10648 10648
Misses 4267 4267
Partials 3 3 Continue to review full report at Codecov.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Do we need instructions on |
@mistercrunch Sure. I'll be happy to add. The instructions would be something along the lines of updating the yarn.lock file whenever you add a new javascript dependency? Anything else you would want me to add? |
(cherry picked from commit f11cde9)
I'm making some improvements to our Dockerfile to better take advantage of the cache. Having a yarn.lock file will make that possible. It is also recommended in the yarn documentation ( https://yarnpkg.com/blog/2016/11/24/lockfiles-for-all/ last line).
Why was it removed in the first place? Is it a good idea to have it here?
I made sure to pull the latest superset version and run yarn before including the yarn.lock file
@graceguo-supercat @john-bodley @mistercrunch