soldeer-commands
| Crates.io | soldeer-commands |
| lib.rs | soldeer-commands |
| version | |
| source | src |
| created_at | 2024-10-07 16:15:15.610954 |
| updated_at | 2024-11-21 14:32:31.657348 |
| description | High-level commands for the Soldeer CLI |
| homepage | https://soldeer.xyz |
| repository | https://github.com/mario-eth/soldeer |
| max_upload_size | |
| id | 1400233 |
| Cargo.toml error: | TOML parse error at line 20, column 1 | 20 | autolib = false | ^^^^^^^ unknown field `autolib`, expected one of `name`, `version`, `edition`, `authors`, `description`, `readme`, `license`, `repository`, `homepage`, `documentation`, `build`, `resolver`, `links`, `default-run`, `default_dash_run`, `rust-version`, `rust_dash_version`, `rust_version`, `license-file`, `license_dash_file`, `license_file`, `licenseFile`, `license_capital_file`, `forced-target`, `forced_dash_target`, `autobins`, `autotests`, `autoexamples`, `autobenches`, `publish`, `metadata`, `keywords`, `categories`, `exclude`, `include` |
| size | 0 |
m4rio (mario-eth)
documentation
README
Soldeer 
Soldeer is a package manager for Solidity built in Rust and integrated into Foundry.
Solidity development started to become more and more complex. The need for a package manager was evident. This project was started to solve the following issues:
- git submodules in Foundry are not a good solution for managing dependencies
- npmjs was built for the JS ecosystem, not for Solidity
- github versioning of the releases is a pain and not all the projects are using it correctly
Installation (Foundry)
Soldeer is already integrated into Foundry. You can use it by running the following command:
forge soldeer [COMMAND]
To check which version of Soldeer is packaged with your Foundry install, run forge soldeer version.
Installation (standalone)
Soldeer is available on crates.io and can be installed with:
cargo install soldeer
Verify installation
soldeer help
Compile from Source
Clone this repository, then run cargo build --release inside the root.
The soldeer binary will be located inside the target/release/ folder.
Usage
Check out the usage guide or Foundry Book.
Changelog
Please see the changelog for more information about each release.
Contributing
See the contribution guide for more information.