We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Depending on the closure library brings in a lot of code that we then have to use closure compiler to remove
In the long run we should invest in dropping these dependencies
This will require an audit but the major pieces are:
goog.asserts
gooog.crypt.base64
goog.object
goog.array
goog.string
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Depending on the closure library brings in a lot of code that we then have to use closure compiler to remove
In the long run we should invest in dropping these dependencies
This will require an audit but the major pieces are:
goog.asserts
, for runtime validation, we should build our own predicate functionsgooog.crypt.base64
we should look into adding our own base64 encoding/decoding librarygoog.object
/goog.array
/goog.string
helpers. We sohuld look into depending on modern platform features instead of these ponyfillsThe text was updated successfully, but these errors were encountered: