Skip to content
New issue

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

blast command does not work after installation: requests for a blast config file #113

Open
Aishat-Akinyemi opened this issue Oct 11, 2022 · 2 comments

Comments

@Aishat-Akinyemi
Copy link

I am unable to run the blast command after successfully installing with npm install cudos-blast -g.

Running any blast command like blast --version or blast --help results in:

BlastError: Config file was not found! Make sure that blast.config.js exists at ~[user]/blast.config.js

@Aishat-Akinyemi
Copy link
Author

Aishat-Akinyemi commented Oct 11, 2022

workaround: manually creating a blast.config.js in my user root directory with this content

module.exports.config = {
  addressPrefix: 'cudos',
  rustOptimizerVersion: '0.12.6',
  gasPrice: '250acudos',

  // optional parameners
  gasLimit: 'auto',
  gasMultiplier: 'auto',
  additionalAccounts: 0,
  customAccountBalances: 1000000000000000000,
  networks: {
    testnet: 'https://sentry1.gcp-uscentral1.cudos.org:36657'
  }
}

@Aishat-Akinyemi
Copy link
Author

Aishat-Akinyemi commented Nov 4, 2022

I'm currently working on a video tutorial so I had to create a new WSL environment and install blast therein.

@nbaum (mentioning you since you reacted to the initial issue), I noticed that the below steps result in an error/unexpected behaviour that could reduce dev-experience:

  • after running npm i cudos-blast global
  • running blast --help results in this error BlastError: package.json not found.Make sure the current working directory is your Blast project's path
  • afterwards I ran blast init in a directory, creating a new cudos/cosmwasm blast project. Running blast --help in this directory works

To further isolate:
-- creating an empty package.json and a blast.config.js as in the root directory (as explained in the workaround in the original issue)

Summarily: Unless you firstly run blast init , there needs to be a blast.config.js, and then a package.json file in a directory before one can run a blast command in that directory.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant