Closed chadoh closed 1 year ago
I ran this with --root-dir .
and it completely wiped my repo LOL, so I dunno if that's very good behavior given the innocuous where to place generated project
help text
Seems like there are a ton of clippy errors in the abundance token, so running make
fails.
This also doesn't work in standalone mode anymore (because the RPC_URL is hardcoded to futurenet). We should either fix that (which I'd prefer) or remove standalone mode (as a stopgap).
The Idea
Rather than use the
@soroban-react
suite of packages, this switches to packages generated by the newsoroban contract bindings typescript
command.Get it Running
You should be able to run
npm run install
andnpm run reset
to get everything set up! Check out the new scripts inpackage.json
to see the magic. Yes, it works with apostinstall
script and generates the libraries directly into thenode_modules
folder. This smells bad but worked better than anything else we tried!You'll also see that there's a
cargo install_soroban
step. This uses theinstall_soroban
alias that's defined in the newly-added.cargo/config.toml
file, and saves it to./target/bin/soroban
. If you want to work with your own local branch of soroban-cli, you can remove the built./target/bin/soroban
and add a symlink there instead pointing at your local CLI build'starget
folder.