rules_nodejs
salsa
Our great sponsors
rules_nodejs | salsa | |
---|---|---|
8 | 16 | |
718 | 2,012 | |
0.4% | 2.4% | |
8.1 | 8.0 | |
8 days ago | 6 days ago | |
Starlark | Rust | |
Apache License 2.0 | 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.
rules_nodejs
- Bazel jasmine_test issue
-
Vercel announces Turbopack, the successor to Webpack
Bazel is just the infrastructure to run webpack. You'd need to do some work to make webpack's state be cacheable (I dunno what options and such it has for this, maybe it's already there as an option). But if you're looking at Bazel for JS work you probably just want to use the existing and maintained rules for it: https://github.com/bazelbuild/rules_nodejs It's been a while since I last looked at it but I don't think it has any caching for webpack.
-
Turborepo 1.2: High-performance build system for monorepos
> Is Bazel designed in a way that make it impossible to do JS monorepos well?
Not impossible, but you really need to go all in with it and follow its conventions and practices. See this for the main docs: https://github.com/bazelbuild/rules_nodejs
One thing in particular that doesn't work well in the bazel world is doing your own stuff outside its BUILD.bazel files. If you're used to just npm install and jam some code in your package.json scripts... that doesn't usually work in the bazel world. If you have a lot of logic or tools in your build you'll likely need to go all in and make bazel starlark rules or macros that recreate that logic. Nothing is impossible, but expect to spend time getting up to speed and getting things working the bazel way.
-
Advice on build scripts and tooling
I am using Bazel with rules_nodejs and Webpack. There's an example here.
-
Help me figure out writing a webapp in Go and JavaScript, with Bazel
It is probably possible to build Angular with ts_project(), however you'd need to manually manage the compiler (Angular has its own) and tsconfig (Angular needs special options). ts_library() does a lot of this for you, so I think it would probably be easier to use that than to force yourself onto ts_project(). The canonical Angular example uses ts_library() FWIW: https://github.com/bazelbuild/rules_nodejs/tree/master/examples/angular
-
Developing in a Monorepo While Still Using Webpack
https://github.com/bazelbuild/rules_nodejs
-
On Bazel Support
Nx is widely used in the Angular community. The Angular team at Google had plans to add Bazel support to the Angular CLI for many years, but the plans didn't materialize. The key folks (e.g., Alex Eagle) working on the effort left Google. Google employees no longer maintain rules_nodejs.
salsa
-
Introducing: Depends
There are some excellent crates already in the Rust ecosystem (notably Salsa) for performing incremental computation, although they generally have different goals to Depends.
-
Vercel announces Turbopack, the successor to Webpack
The content of that "Core Concepts" page sounds a lot like https://github.com/salsa-rs/salsa
-
Is there anything like funflow for rust?
I know of salsa, but I don't know if it can persist changes to disk (and my guess from looking at this issue is that it can't).
- Non-lexical lifetimes (NLL) fully stable | Rust Blog
-
The biggest new idea in computing for half a century was just scrapped
- the practical approach to this is to split workload into work units (aka tasks/queries/etc.) and then force information flow through centralized "request"/"query" APIs that automatically track dependencies - see https://github.com/salsa-rs/salsa for more information
-
Is there any research or articles on different, more efficient compiler designs?
This, and as pointed Salsa.
-
Trying to understand the paper "Efficient and Flexible Incremental Parsing" (incremental LR)
These guys might be of interest for you, they think a lot about incremental parsers. https://github.com/salsa-rs/salsa
-
Announcing avalanche 0.1, a React- and Svelte-inspired GUI library
salsa-rs authored by niko matsakis and other top rust devs
-
Is GO a good option to write a compiler/interpreter?
Some optimizations are not easy with Go. For example caching like in Rust Analyser Salsa Framework
-
Will rust ever have a futures executor in std?
How would this differ from salsa (https://github.com/salsa-rs/salsa) and the query-driven approach used by rustc?
What are some alternatives?
jazelle - Incremental, cacheable builds for large Javascript monorepos using Bazel
Benthos - Fancy stream processing made operationally mundane
bazel-skylib - Common useful functions and rules for Bazel
Disruptor - High Performance Inter-Thread Messaging Library
rules_docker - Rules for building and handling Docker images with Bazel
papers-we-love - Papers from the computer science community to read and discuss.
bazel-coverage-report-renderer - Haskell rules for Bazel.
differential-dataflow - An implementation of differential dataflow using timely dataflow on Rust.
bazel-linting-system - πΏπ Experimental system for registering, configuring, and invoking source-code linters in Bazel.
rust-signals - Zero-cost functional reactive Signals for Rust
rules_rust - Rust rules for Bazel
ocaml-multicore - Multicore OCaml