cargo-watch
just
Our great sponsors
cargo-watch | just | |
---|---|---|
22 | 165 | |
2,606 | 17,053 | |
1.7% | - | |
6.7 | 9.1 | |
4 months ago | 5 days ago | |
Rust | Rust | |
Creative Commons Zero v1.0 Universal | Creative Commons Zero v1.0 Universal |
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.
cargo-watch
-
Cryptoflow: Building a secure and scalable system with Axum and SvelteKit - Part 0
I used cargo-watch here so that every time my source changes, the server will automatically restart and re-serve the updated code.
-
Use just to manage Rust project commands
watch-one-test test_name: # More info on cargo test: https://doc.rust-lang.org/cargo/commands/cargo-test.html # More info on cargo watch: https://github.com/watchexec/cargo-watch cargo watch -x check -x 'test -- --test-threads=1 --nocapture {{test_name}}' -c -q
-
Functional Programming 1
Rust: RPDS https://docs.rs/rpds/latest/rpds/ and Im https://docs.rs/im/latest/im/
Rust isn’t great for letting you do FP things like other languages, but it does have the best type system imho which makes it the leading functional programming language right now imho. If you’re not using too many specialized python packages then I recommend using Rust instead, even for toy demos, as you can be more confident your code works without needing to run it and wait for a crash like you would in debugging python, and the tests also run faster in rust due to the incremental compilation. Use cargo-watch and you can retest your code every time you save your work.
https://github.com/watchexec/cargo-watch
I usually write a make command to cargo watch and rerun each test file : code file pair independently so then you won’t rerun your tests in other modules when you change the one you work on (faster but might miss stuff if you change API contracts which touch other parts of your codebase)
-
Are there any continuous testing tools with real-time line-by-line IDE feedback for Rust?
you can use cargo-watch to real time run tests on save in your attached vs code console session which is about as close to what you're asking as I think exists for rust
-
Why does the "crate" nomenclature include both "binary" and "library"?
Note that cargo, by virtue of being a package manager for a programming language, is primarily going to be dealing with library packages. That's not because it can't manage executables (see cargo-watch for a particularly useful example), it's just that it's less common.
-
Help me love Rust - compilation time
Also check out cargo-watch -- https://crates.io/crates/cargo-watch
-
cargo-watch hangs on reload
Unless there's a new issue, I think this is what was here: https://github.com/watchexec/cargo-watch/issues/249
- Cargo Watch 8.3.0
- Cargo Watch v8.2.0
-
Creating Rest APIs with Rust
A feature that I look for whenever possible in my development environment is Hot Reload, with it, every time a file is changed and saved the application restarts, so the cycle of writing-evaluating-refactoring code becomes extremely fast, for Rust, we have cargo watch, I suggest taking a look at the documentation for more details.
just
- Just a Command Runner
-
Ask HN: Any tool for managing large and variable command lines?
I started using just [0] on my projects and have been very happy so far. It is very similar to make but focused on commands rather than build outputs.
Define your recipes and then you can compose them as needed.
[0] https://github.com/casey/just
-
Ask HN: What software sparks joy when using?
just - https://github.com/casey/just
-
GitHub switched to Docker Compose v2, action needed
Welp there is absolute chaos in that thread -- guess it's not an April Fools joke.
I wonder if relying on CI for anything other than provisioning machines is a mistake -- maybe we should have never moved from doing things from local scripts written in $LANGUAGE.
That said, I'm probably biased since I'm a massive fan of things like `make` and more appropriately for the current age, `just`[0]
[0]: https://github.com/casey/just
-
Which command did you run 1731 days ago?
> When a command has some cognitive requirements I create a script with some ${1:-default} values and I store them all in $PATH enabled local/bin
I would consider using just for this:
https://github.com/casey/just
-
Using Make – writing less Makefile
Your coworker's experience is more principled: Make is a mediocre tool for executing commands. It wasn't ever designed for that. Although it is pretty common to see what you are mentioning in projects because it doesn't require installing a dependency.
For a repo where an easy to install (single binary) dependency is a non-issue, consider using just. [1] You get `just -l` where you can see all the command available, the ability to use different languages, and overall simpler command writing.
[1] https://github.com/casey/just
-
Show HN: Just.sh – compiler that turns Justfiles into portable shell scripts
This is fantastic, but I'd say that this solution is somewhat in response to this open issue from 2019:
https://github.com/casey/just/issues/429
I really wish just was included as a package in distributions.
-
Sharing Saturday #496
So far, I didn't work on new features at all but on stabilizing the ground for further development: 1. CMake lists and modules were rewritten a lot, now managing builds and their configurations is much lesser pain. 2. Brought in Justfile for regular tasks, and it's great, no less. 3. Linters, formatters, analyzers for almost all the code (except for Janet for now, as because of it being a niche and young technology, it didn't get enough attention yet). 4. ECS stub. Now runtime class doesn't look like a god object. 5. Started writing unit tests which didn't happen with my personal projects before and maybe indicates how serious am I about this one :D 6. Some of previously hardcoded data has been moved to INI files. Now, if I release the game in 10 years, and in 10 more years some eccentric person decides to make a variant of it, it will be slightly simpler.
-
What’s with DevOps engineers using `make` of all things?
i've grown to like this for my personal projects. https://github.com/casey/just
-
Show HN: Jeeves – A Pythonic Alternative to GNU Make
Reminds me of `just`. Which I love.
https://github.com/casey/just
What are some alternatives?
cargo-check
Task - A task runner / simpler Make alternative written in Go
cargo-multi - Extends cargo to execute the given command on multiple crates - upstream is at
cargo-make - Rust task runner and build tool.
cargo-count - a cargo subcommand for counting lines of code in Rust projects
cargo-xtask
cargo-script - Cargo script subcommand
Taskfile - Repository for the Taskfile template.
Cargo - The Rust package manager
CodeLLDB - A native debugger extension for VSCode based on LLDB
cargo-outdated - A cargo subcommand for displaying when Rust dependencies are out of date
cargo-release - Cargo subcommand `release`: everything about releasing a rust crate.