Ryan

The problem stems from the linker calculating import hashes based on file contents before replacing the imports contained in the file. So in the case of two different versions of...

Old versions should already be getting aliased as a byproduct of the hash replacement in import statements. We _could_ require versions as part of the import paths, though, to enforce...

On further reflection, I favor fixing the current functionality so it works as expected and augmenting the logger so it shows package names and versions along with types. It's almost...

Yes, at the moment it's not possible to reference two different versions of a package in one file. Aliases don't help this at all because the import hashes are based...

I feel like I can see both sides to this one, since removing the extra sources could simplify the codebase and since one could argue including additional installation sources might...

Yeah, it is. Enabling installation from IPFS hash would basically just be a matter of changing the place from where the hash is pulled.

Environments should definitely be named after chains, as they communicate information about chain states. `.dapplerc` should also allow different chains to have different connection settings so the user can take...

> Not sure this is a degree of freedom worth adding. Agreed. What do you intend to achieve by using block hashes as chain names? Are the block hashes supposed...

Okay, I understand what you're asking for now. That sounds like a good goal to me. The map could just consist of setting keys to string values, which is something...

@nmushegian, any further input on this?