-
Notifications
You must be signed in to change notification settings - Fork 58
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
Use latest gb master as per July 2nd, 2018 #61
Changes from all commits
9279c8b
8acfb86
0619a90
d13d984
771dbf6
356977b
0c8697f
59670a1
254446c
0150dae
0dacdab
b032829
aac9681
efc1a09
6f909f9
ecb5baf
e0c59f2
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -6547,6 +6547,10 @@ remark-parse@4.0.0: | |
vfile-location "^2.0.0" | ||
xtend "^4.0.1" | ||
|
||
rememo@^3.0.0: | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. The only downside of the current setup is that we need to ensure that all npm packages are referenced in There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. True, thankfully, the ones missing get reported by Metro when |
||
version "3.0.0" | ||
resolved "https://registry.yarnpkg.com/rememo/-/rememo-3.0.0.tgz#06e8e76e108865cc1e9b73329db49f844eaf8392" | ||
|
||
remote-redux-devtools@^0.5.12: | ||
version "0.5.12" | ||
resolved "https://registry.yarnpkg.com/remote-redux-devtools/-/remote-redux-devtools-0.5.12.tgz#42cb95dfa9e54c1d9671317c5e7bba41e68caec2" | ||
|
@@ -7409,6 +7413,10 @@ timers-browserify@^2.0.2: | |
dependencies: | ||
setimmediate "^1.0.4" | ||
|
||
tinycolor2@^1.4.1: | ||
version "1.4.1" | ||
resolved "https://registry.yarnpkg.com/tinycolor2/-/tinycolor2-1.4.1.tgz#f4fad333447bc0b07d4dc8e9209d8f39a8ac77e8" | ||
|
||
tmp@^0.0.33: | ||
version "0.0.33" | ||
resolved "https://registry.yarnpkg.com/tmp/-/tmp-0.0.33.tgz#6d34335889768d21b2bcda0aa277ced3b1bfadf9" | ||
|
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.
Should we put it in the shell script and run as
postinstall
script for the repository?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.
Perhaps. I refrained from automating it from the beginning so to give us time/space to see how we use it actually but, I can give it a try now and see.
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.
So, gave
postinstall
. Our patterns these days involve more than a fewyarn install
attempts and that will causenpm i
to be called too many times, unnecessarily. Ideally, we wantnpm i
to be called rarely, like, when the GB repo is cloned or when the GB branch is changed.I think we can leave
npm i
out of automation for the following days/weeks and re-assess, depending on the patterns we notice.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.
And btw, thanks for the review @gziolo !