Filip Tibell

I can second how useful this would be for us, right now we're unable to completely manage our tools in CI using neither foreman nor aftman. Foreman does not match...

I would love a more extensible Fusion, where more functionality can be added on top as needed. > Here's a rough idea of how that could work... That rough idea...

This is one of the first things that I made a utility function for when starting with Fusion, and would be a great addition. Being part of the public namespace...

Turns out this is simply due to how unix-like OSes handle subprocesses, the issue has been solved in https://github.com/LPGhatguy/aftman/commit/d3f8d1fac4c89d9163f8f3a0c97fa33b91294fea and foreman would need to do something similar.

> I am able to rename `tab`, `foo` and `bar` in these examples - are you not able to do so? Whenever I try to rename anything in the example...

Made a PR for splitting the trust check from installation in https://github.com/LPGhatguy/aftman/pull/30 and would like to try and implement this as well. > We'll need to take some care to...

> I think we should also support other archive formats if they come up in practice. Another tool that we use releases tarballs for unix platforms and zip files for...

> I think we're relying on the `Ord` implementation of `Architecture` for this. The hope is that on systems that support AArch64 AND x86-64, we should pick AArch64. The opposite...

If I remember correctly one of the primary reasons for making my sourcemap PR was that this issue (and related PR https://github.com/rojo-rbx/rojo/pull/337) not going through was blocking something I wanted...

Just discovered a use-case for this that sourcemaps wouldn't really solve - auto-discovery of serve sessions for specific project files! Imagine you have a VSCode extension or somesuch that inspects...