rules_js
High-performance Bazel rules for running Node.js tools and building JavaScript projects (by aspect-build)
mutant
Automated code reviews via mutation testing - semantic code coverage. (by mbj)
Our great sponsors
rules_js | mutant | |
---|---|---|
2 | 5 | |
279 | 1,925 | |
1.4% | - | |
9.4 | 8.2 | |
7 days ago | 7 days ago | |
Starlark | Ruby | |
Apache License 2.0 | Nonstandard |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
rules_js
Posts with mentions or reviews of rules_js.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-07-17.
-
Any nice patterns for releasing libraries?
For Bazel you can find a good example of this functionality in rules_js with the integration of pnpm workspaces and the npm_package rule (macro) which recently gained a .publish runnable target that will publish the package.
-
An ex-Googler's guide to dev tools
I also think it is partly as the tooling is not there yet - especially in the typical case when a project depends on lots of external dependencies.
I am looking forward to new set of bazel rules being worked on for eg. https://github.com/aspect-build/rules_js and https://github.com/jvolkman/rules_pycross which will makes it more idiomatic to work with existing language ecosystems.
mutant
Posts with mentions or reviews of mutant.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-07-17.
-
An ex-Googler's guide to dev tools
There's a pretty good Ruby gem I've used for this before:
https://github.com/mbj/mutant
-
Code coverage vs mutation testing.
You should only really care about mutation testing if your code coverage is relatively high. If your code coverage is 20% then mutation testing should not be your priority. We use mutation testing (mutant for Ruby, pitest for Java). mutant is pretty hassle-free but only works when running under MRI so if you use jruby you are out of luck. pitest was far less easy to integrate.
- Mutant – Automated code reviews via mutation testing – semantic code coverage
- Automated code reviews via mutation testing - semantic code coverage.
-
Semantic blind spot in Ruby case statement
mutant shows redundant semantics, why we'd like to reduce them is perhaps better explained at https://github.com/mbj/mutant#what-is-mutant