Error with cargo install on windows machine about rojo

[Dekkonot]

This is an issue we need to address but it isn't our fault; one of the dependencies downstream broke semver, which has caused compilation issues for multiple crates. A prime example is cargo-watch.

Temporary fix for now is to use --locked when running cargo install, but I will look into what happened and how we can handle it.

[Dekkonot]

This was a fun adventure. It turns out that Notify, our file watcher, wasn't enabling some cargo features it needed to. This meant that when a dependency, winapi-util, updated, it resulted in a build that would normally succeed starting to fail.

The solution is for notify v4 to enable std and winerror as cargo features. I've opened an issue here. If it gets closed without being fixed (let's be frank, Notify v4 is very out of date at this point) then we'll have to upgrade our file watcher.

Going to leave this issue open until the one on Notify gets closed one way or another.

[Dekkonot]

This should be resolved since Notify has made a new patch. Let me know if it's still a problem!