protocolbuffers / protocolbuffers/protobuf-javascript
Should `goog.DEBUG` be false for builds distributed via npm?
Open
Nobody has claimed this yet.
help wanted
packaging & distribution
triaged
- Dominant language
- JavaScript
- Stars
- 471
- Forks
- 91
- Avg merge
- 3h 57m
- Merged PRs (30d)
- 2
Description
goog.DEBUG is true in the google-protobuf.js runtime distributed in the npm package. This setting gates the various assertion code in the runtime (goog.asserts.ENABLE_ASSERTS = goog.DEBUG;).
- Is this expected?
- If so, should DEBUG be set to false for production builds? And should two builds be distributed, or a means be exposed to configure this?
- If not, should the gulpfile that generates the runtime supply
--define goog.DEBUG=falseto the closure compiler invocation?
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
Read closure/goog/base.js at lines 224-230 and inspect the gulpfile's Closure Compiler invocation. Compare the generated google-protobuf.js runtime in the npm package with the intended production behavior, then determine whether the build should change, expose configuration, or distribute multiple builds.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100