-
Notifications
You must be signed in to change notification settings - Fork 904
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
Get closure-library from google-closure-library. #2509
Get closure-library from google-closure-library. #2509
Conversation
…e-builder so we can control the version directly.
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.
As a Closure expert, this LGTM to me.
(I did check and it builds fine for me).
@@ -16,6 +16,7 @@ | |||
"license": "Apache-2.0", | |||
"devDependencies": { | |||
"closure-builder": "2.3.8", | |||
"google-closure-library": "^20200101.0.0", |
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.
We don't use version ranges in the Web SDK. Not that it matters for this versioning scheme, but it might be better to be consistent and drop the ^
.
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.
Oops! I just did "npm install --save-dev" or some such... Thanks. I'll remember this for next time!
@hsubox76 Can you approve the yarn.lock change? |
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.
Looks good!
Get closure-library from google-closure-library instead of via closure-builder so we can control the version directly.