Skip to content

Releases: watchexec/cargo-watch

v7.0.0

21 Aug 05:38
Compare
Choose a tag to compare

#89 — On Windows, better support for ignores — breaking

v6.0.0

12 Sep 06:20
4810b53
Compare
Choose a tag to compare
  • Breaking: change default value of --delay to 0.5 seconds
  • Dependency: update to watchexec 1.8.5
  • Watchexec: apply --delay value to debounce time as well as poll interval

5.1.0

26 Jul 12:49
3cc929e
Compare
Choose a tag to compare
  • Feature: --no-restart flag (#73)
  • Docs: new article for inotify limits (#72)

5.0.5

25 Jun 14:22
eda5012
Compare
Choose a tag to compare
  • Fix: parse --delay from seconds instead of mistakenly interpreting the argument as milliseconds (#72)
  • Doc: add "No space left on device" error to troubleshooting section (#72)

5.0.4

20 May 05:45
00fb1bd
Compare
Choose a tag to compare
  • Improvement: change the current directory to the cargo root at the top level, not at the subcommand level. That should improve #71 while still supporting #70.

5.0.3

13 May 14:05
d606a17
Compare
Choose a tag to compare

Bugfix: support directories/paths with spaces (#70)

5.0.2

10 May 23:16
8919764
Compare
Choose a tag to compare

5.0.1: more version control ignores

29 Apr 00:50
a23d2dc
Compare
Choose a tag to compare

Following from watchexec 1.8.3, corrected the .git ignore glob and added ones for .hg and .svn.

Version 5.0.0: A New Hope; aka Just Wrap Watchexec, Properly This Time

27 Apr 13:36
66b83f9
Compare
Choose a tag to compare

This is the proper way to implement Version "5".

In a major break from the past, Cargo Watch now depends directly on Watchexec. It uses the newly-landed (contributed by yours truly) library support in watchexec to directly and statically embed it, parsing our own options and figuring out our own defaults and then running watchexec's main loop with the relevant arguments.

This means that we take advantage of Watchexec's excellent features and fixes in this domain, and can focus entirely on the cargo experience and the specific concerns around it. Notably, this fixes:

You can install as usual with

$ cargo install cargo-watch

And upgrade an existing install with:

$ cargo install --force cargo-watch

If you had previously installed the watchexec binary to make the wrappy version work, and you do not require it anymore, you can safely uninstall it. However, watchexec itself is a great tool and may suit other non-cargo usecases you have well, so consider keeping it.

Version "5" aka Just Wrap Watchexec

18 Apr 05:31
0308fd0
Compare
Choose a tag to compare

I've written a new version that calls watchexec by translating cargo watch's options and defaults, so given that watchexec has several issues of ours covered, technically these are fixed:

It's a bit of a cheat, though.

You can install with this lengthy command:

$ cargo install --git https://github.com/passcod/cargo-watch --branch just-wrap-watchexec

And if you don't have it already, you'll also need to $ cargo install watchexec.

This is not published to crates.io because I haven't completely given up on making my non-wrappy version work, so if I publish further non-wrappy releases they'll go on crates.io on the 4.x release boat.