protocolbuffers / protocolbuffers/protobuf-javascript
Remove dependencies on closure library
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 471
- Forks
- 91
- Avg merge
- 3h 57m
- Merged PRs (30d)
- 2
Description
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.base64we should look into adding our own base64 encoding/decoding librarygoog.object/goog.array/goog.stringhelpers. We sohuld look into depending on modern platform features instead of these ponyfills
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files or tests are named. Begin with an audit of the Closure Library dependencies, especially goog.asserts, gooog.crypt.base64, and the goog.object/goog.array/goog.string helpers, then inspect how Closure Compiler removes them; the work is done when the listed dependencies have viable replacements and the project no longer depends on the Closure Library.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- build-system
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100