We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
#9 introduced more friction into the build step, and we should update the setup guide when we find the chance.
We also built stride-build instead of simply using stride's proto files because of type conflicts + duplicates (related to #10)
To sum up, we probably manually built and removed some directories.
The text was updated successfully, but these errors were encountered:
git submodule sync --recursive git submodule update --init --recursive
If there are any branches you should be using instead:
cd stride git checkout <branch> git pull origin <branch> cd ../ cd cosmos git checkout <branch> git pull origin <branch>
npm run codegen:build
mkdir -p stride-build cp -r ./stride/build/* ./stride-build
Afterwards, remove files or directories as needed
Taken straight from the README
npm run codegen npm run buidl
Sorry, something went wrong.
Added here 422d949
No branches or pull requests
#9 introduced more friction into the build step, and we should update the setup guide when we find the chance.
We also built stride-build instead of simply using stride's proto files because of type conflicts + duplicates (related to #10)
To sum up, we probably manually built and removed some directories.
The text was updated successfully, but these errors were encountered: