bazelbuild / bazelbuild/rules_closure
entry_points & closure_js_test
- Dominant language
- Java
- Stars
- 159
- Forks
- 111
- PR merge metrics
- No merged PRs in 30d
Description
When using `goog.module` and `closure_js_test`, simply adding a `testSuite` is insufficient to avoid dead-code-eliminating the tests. One must add `entry_points= ["goog:$MY_TEST_PACKAGE"]` to the `closure_js_test` invocation. Please either fix the documentation to make this more clear, or eliminate the need for the use of `entry_points`.
Contributor guide
Research direction
Start with the documentation for closure_js_test and the handling of entry_points when using goog.module and testSuite. Determine whether the issue should clarify the required entry_points setting or remove that requirement. Done means the documented behavior is clear or the need for entry_points is eliminated, with the relevant test or example updated if one is found.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- build-system, tooling
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100