homebrew-tap
rules_js
| homebrew-tap | rules_js | |
|---|---|---|
| 1 | 2 | |
| 6 | 281 | |
| - | 1.1% | |
| 8.8 | 9.5 | |
| 13 days ago | 2 days ago | |
| Ruby | Starlark | |
| - | Apache License 2.0 |
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.
homebrew-tap
-
An ex-Googler's guide to dev tools
https://graphite.dev/
> Join the waitlist
:-(
Since you seem to be in the beta, you may want to let them know their Homebrew tap is pointing to the wrong GH org: https://github.com/withgraphite/homebrew-tap/blob/master/For...
rules_js
-
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.
What are some alternatives?
rules_pycross - Bazel + Python rules for cross-platform external dependencies
clusterfuzz - Scalable fuzzing infrastructure.
redirector-rs - A dead simple human-writable URL redirector based loosely on google's `go/` system.
mutant - Automated code reviews via mutation testing - semantic code coverage.
rules_docker - Rules for building and handling Docker images with Bazel
scalar - Scalar: A set of tools and extensions for Git to allow very large monorepos to run on Git without a virtualization layer